-
Support
- Why can't ItemPath reach Web Services?
Business
-
Account & Licensing
-
Installing & Updating
-
Power Pick Connections
-
Users & Permissions
-
Data Push & Data Pull
-
API
-
Reports
-
Snapshots & Dashboard
-
Workflows
Why can't ItemPath reach Web Services?
Issue:
The Web Services connection is returning "Unable to connect to Web Services URL / IP address"
Resolution:
Check port-forwarding, firewall, whitelisting, and network rules, and see if traffic can be seen coming from ItemPath's IP address.
If ItemPath is unable to reach Web Services, there is usually a network issue that needs to be resolved.
Using network tools, check your network traffic to verify that you are seeing requests from the ItemPath IP address.
- For Cloud installations, this IP will be sent to you in your welcome email
- For On-Premise installations, this IP will be where ItemPath is installed
If traffic can be seen from ItemPath, you can then test that the Web Services public IP/port is reachable.
Next, check the following:
- Is the dedicated IP and port number (if changed from the default port 1353) for your machine running the Power Pick Cross Enterprise Unit service correct?
- For ItemPath hosted in the cloud, is the dedicated IP address a public IP accessible outside of internal networks?
- Has port forwarding has been set up for the correct IP/port number?
- Has the ItemPath IP address been whitelisted in the firewall rules?