Installation of modules fails - proxy

[sdoyle]

Hi,

Currently on a trial on premise installation. Attempting to download additional module e.g SQL results in a failure error 302  found. We are behind a proxy server but the pulseway server is configured to use the proxy.

Regards,

Shane

[sdoyle]

Seems to be getting stuck in our UAG gateway...any guidance?

[Chris]

Hi Shane,

Did you also configure the Pulseway agent to use the proxy? Does your proxy require authentication? If so, what authentication mechanism does it use?

Chris

[sdoyle]

Hi Chris,

The above posts can be deleted. 

We are now publishing pulseway enterprise without UAG and are still behind a zscaler proxy. Pulseway is working in all aspects except for the following:

* Update check from Pulseway server fails
* No additional modules will download
* Refresh server license - "Something went wrong - unable to  connect to remote server"

We have proxy authentication and ssl scanning turned off for this particular server based on ip address of the server. 

 

Shane

[Chris]

Hi Shane,

Can you also bypass the proxy for the following hosts on the Enterprise server?

slv.pulseway.com
slv2.pulseway.com

Chris

[sdoyle]

Hi Chris
We bypassed proxy and firewalls for the above and still get errors such as

Module StorageCraft Cannot be downloaded right now. The error was: Cannot find the latest version for StorageCraft Server module

Would the fact we are still on a trial license have anything to do with this?

 

Regards,

Shane

[Chris]

Hi Shane,

No, Pulseway trials allow you to try all features of product without any limitation. Restart the IIS server and then try again in 5 minutes. If this doesn't work please send an email to support [at] pulseway [dot] com and I'll escalate it to L2 technical support.

Chris

[sdoyle]

Hi Chris,

Thanks yet again. Still no success. I have made contact with Paul and will work it out with him. Will update this when I find out what was wrong.

 

Shane

[sdoyle]

Hi CHris and Paul,

 

Thanks for the support. Our firewall team finally made the changes outlined above - direct access to

slv.pulseway.com
slv2.pulseway.com

 and it is working a treat. Happy for this to get locked.

[Chris]

Hi Shane,

Thank you for your confirmation. Enjoy using Pulseway!

Chris