→ 🚀What's New? Join Us for the Fall Product Launch! Register Now !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
DriesVda
Engaged Sweeper

Hi all,

I'm struggling with getting the warranty scan functional again since we switched to a different proxy.

Already ran the report to show me the potential error for warranty scanning.
I see two main errors appears, being:
Unknown error: Connection error: Connection error: An error occurred while sending the request.
Unknown error: Connection error: Connection error: The ServicePointManager does not support proxies with the https scheme.

Our proxy is an HTTPS URL, but for the sake I tried with http as well.
The proxy does not require authentication (checked with our IT security)

DriesVda_0-1705391371551.png
On the lansweeper server (Windows Server) the proxy is also configured, although I'm not sure if this is needed or if the proxy settings in "server options" is sufficient.

Our setup:

DriesVda_1-1705391545221.png

Does anyone have an idea how to continue the troubleshooting or is there anyone else who has experience with this kind of setup with a cloud proxy (zscaler in our case)?

 

1 ACCEPTED SOLUTION
DriesVda
Engaged Sweeper

Seems like changing the URL to http + keeping authentication off/unchecked was the solution anyway. Just had to have a little patience before the warranty results were populated correctly 🙂 

View solution in original post

2 REPLIES 2
DriesVda
Engaged Sweeper

Seems like changing the URL to http + keeping authentication off/unchecked was the solution anyway. Just had to have a little patience before the warranty results were populated correctly 🙂 

David_GF
Lansweeper Tech Support
Lansweeper Tech Support

@DriesVda The proxy configuration in Configuration > Server Settings in the Lansweeper web console should be enough. The error The ServicePointManager does not support proxies with the https scheme points to an authentication issue with https, as that .net class does not support https by default. HBowever, using http should fix it, as you've tried, IF http is enabled in your proxy. 

Even if user/pwd authentication is not used in your Zscaler proxy, there are other authentication methods that might be in place, such identity proxy or a client app. Best is to double check with your IT Security team about it.

If there isn't any authentication in place, and http is enable on your proxy, we should do a more in-depth troubleshooting. For that is better to open a support ticket: https://www.lansweeper.com/contact/contact-support/



~~~~~~~ (〃 ̄︶ ̄)人( ̄︶ ̄〃) ~~~~~~~
Sweep that LAN, sweep it!