Troubleshooting Publisher - NPA

Userlevel 2
Badge +9



I set up a new contingency publisher for the priv app, ran troublesshoint on the tool and everything is fine, no problems.

But I can't access priv app,
ran a curl , and got an http 500 return.
We are not using DNS in the browser.

Has anyone ever experienced this ? Or do you have an idea why?

2 replies

Userlevel 3
Badge +14

After you configured everything in the Netksope console, did you immediately try to connect? I ask, as to connect immediately & enforce/pull the changes made in the console you need to check for config update on the agent and disable/reenable the agent.  

Normally end user machines would just get the updated configuration at the agent refresh interval.  

Userlevel 2
Badge +9

Yes, I disabled and dwelt again.

Weird I can trigger ping and telnet, netskope troubleshooter has no errors