16 Posts
0
60
Remote Shadow (P2P) - system\ network and firewall requirements
I am testing the new Remote Shadow (P2P) connections from our WMS Cloud tenant. I believe our zero-trust networking is blocking the connections. What are the requirements to allow this functionality? URLs, ports other settings to allow the connection.
When I test from outside our corporate network the connection is successful.
Thank you for any direction you can provide.
Mike Zirbes
16 Posts
0
February 22nd, 2024 16:28
Resolved by using the correct URL to access WMS.
https://us1.wysemanagementsuite.com
buffalobound
3 Apprentice
3 Apprentice
•
709 Posts
0
February 13th, 2024 14:06
P2P requires min of ThinOS 2311.
Communication is over the 443 SSL that is already required, so no special ports, but a new URL/FQDN is required for relay if you have restrictions in place.
URL
Primary IP
Secondary IP
Port/Protocol
us1-relay.wysemanagementsuite.com
20.42.152.134
52.167.12.59
443/TCP
Mike Zirbes
16 Posts
0
February 22nd, 2024 15:04
Still having problem from behind our corporate firewall. We are seeing this error:
Access to XMLHttpRequest at 'https://us1.wysemanagementsuite.com/ccm-web/admin/device/1549303/getWebRTCStatus' from origin 'https://us1.cloudclientmanager.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
from my small amount of searching, it sounds like this is a server-side configuration issue.