DeviceHQ listening ports
- This topic has 1 reply, 2 voices, and was last updated 5 years, 9 months ago by
.
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: AEP Model › DeviceHQ listening ports
Steve Kovarik.
Bob DoironHi,
We’ve been placing our own equipment at customer sites for a while now and one issue we ran in to over and over again was outbound firewall filtering. Very often they lock down their network and only open outbound ports by exception – often only port 80 and 443 to allow web browsing.
How does the AEP conduit connect to DeviceHQ? i.e. What ports at DeviceHQ is it connecting to? I placed ours behind a locked down router and it no longer checks in, so I suspect it isn’t using http/https connections.
Is there a way around this issue?
Steve KovarikHi Bob
In the Conduit “Remote Management” screen if SSL is unchecked (disabled)
then TCP port 5799 is used. If SSL is checked (enabled) then TCP port 5798 is used to check-in to DeviceHQ.
-Best Regards