Getting internal server error while hitting deploy API endpoint


Badge +7

Hi, 

I am getting internal server error while hitting below POST query through swagger/ postman https://alliances.goskope.com/api/v2/policy/urllist/deploy

I have provided all the required permission while creating token to make the request, not sure why I am getting this error.

https://alliances.goskope.com/apidocs/?include_beta_routes=0#/policy/post_api_v2_policy_urllist_deploy

 

Am I missing anything ? Please help me out with this issue.

 

Thanks,

Sakshi


19 replies

Badge +13

Hi Sakshi

Welcome to the community!

I see you are using the endpoint for "POST URL List Deploy (Apply Changes)". Which steps have you performed beforehand, e.g. any URL list modifications? Did those succeed?

Did you confirm the token is being sent in the header?

 

cheers

Rudi

Badge +7
Hi Rudi,
 
I am using PATCH https://alliances.goskope.com/api/v2/policy/urllist/441/append to append url to a specific list and it is getting reflected when I hit GET request to https://alliances.goskope.com/api/v2/policy/urllist/441/
 
But to reflect these changes in Netskope dashboard I need to run deploy endpoint which is giving me error.
 
And yes I am passing valid token with all required permission in header.
 

 

Regards,

Sakshi

Badge +13

Sakshi,

I cannot replicate the 500. And yes, it looks like your token is correct (or it would throw a different error).

You could review the unapplied URL list in the tenant UI (how it looks there) and try to apply from there, as a basic test. 

Badge +7

Hi,

I am able to apply changes through dashboard , and it is getting reflected in list also.

But still getting internal server 500 error through API. Any idea what could be the reason , as I am able to hit other endpoints successfully.

 

Badge +7

Hi,

Do we need to make any change in permission in Netskope UI for deploy endpoint https://alliances.goskope.com/api/v2/policy/urllist/deploy to work.

 

Can you please help me out with this issue.

 

Sakshi

Badge +13

Sakshi,

you only need to ensure that the respective endpoint is enabled:

(under Settings > Tools > REST API v2)

Existing tokens will be updated, they don't change. Same goes for expiration date, btw.

Hope this helps! 

cheers

Rudi

 

Badge +7

Hi Rudi,

 

I have already provided the required permission, still it is giving us same internal sever error 500. What can we do now?

 

Sakshi

Badge +13

Sakshi

to me, it looks configured correctly. I suggest you open a Support case, mentioning what you've tested so far. (You might want to refer to this thread as well, so that the Support engineer does not have to start from scratch).

Thank you for your cooperation! 

cheers 

Rudi

Badge +12

Hello @SAKSHI , @rkessler ,

 

Did you check the curl call command displayed from the swagger in Tools > REST v2 > API DOCUMENTATION > urllist/deploy > TEST IT ?

 

I used the deploy endpoint with no issues from swagger.

 

Kind regards,

Ă’scar

Badge +7

 

Not working from here as well

Badge +13

@oscar excellent idea.

@SAKSHI please change your token immediately, as it's visible in your screenshot.

Badge +7

@rkessler @oscar That was an expired token , have created new one now.

I'll open Support case for this issue , thanks!

Badge +7

@rkessler @oscar Hi, I am unable to log in Support portal using my credentials , Can you please help me.

Badge +13

Sakshi

the support portal has been migrated to a new system recently. If you haven't opened a ticket in the past 4 weeks or so, it is necessary to reset your PW. Please use the "forgot my pw" option. Thank you for your cooperation! 

Badge +7

Already did that but not receiving any mail on registered email Id.

Badge +5

I'm also unable to access the new portal - no email coming to Deloitte account email. 

Badge +15

@SAKSHI  I would send an email to support@netskope.com to resolve your issue.  

Badge +15

@marmurray

 

You can always reach out to our support team via email at support@netskope.com. To best handle your request, please provide the following information:

  • Nature of the request (please provide as much detail as possible and screenshots if you have them)
  • Level of urgency
  • Number of users affected
  • Contact details for getting in touch with you or an appropriate member of your team to address the issue
Badge +7

Thanks @JulieB , We are stuck with this error for quite some time , so would really appreciate if someone can help us to resolve this issue.

Reply