Use none standard ports
See original GitHub issueHi all,
I’ve just changed ISP and there is something odd going on with accessing my server at home on port 443, I have found that other ports work reliably.
I have tried to redeploy the skill (from master is this the best branch to use?) with config.js file populated; for the url I have something like this;
baseURL: 'https://openhab.my.domain:8443/rest',
but I’m not having any luck.
I have checked the url from my mobile and am presented with a basic login page, which I can login to and am able to get to the rest page.
Should this work, or is changing the port not supported?
Thanks.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
What are non-standard ports and protocols [closed]
A non-standard port just means a service running on a port other than its default, usually as defined by the IANA port numbers...
Read more >Port Confusion - Is Security Through Obscurity Bad?
Discusses the pros and cons of using non-standard ports. It's a form of "security through obscurity". But is it really bad practice?
Read more >Non-Standard Port, Technique T1571 - Enterprise
ID Name Description
G0099 APT‑C‑36 APT‑C‑36 has used port 4050 for C2 communications.
S1016 MacMa MacMa has used TCP port 5633 for C2 Communication.
S1031 PingPull...
Read more >Non-Standard Port Usage
Non-Standard Port Usage ... Identifies the apps using ports that are non-standard for them (the app's standard port is defined by App-ID). Also ......
Read more >HTTP/HTTPS requests to non-standard ports on the CLoud ...
In case the access method in use is WSS Agent, you can configure the forwarding ports in your portal account at Service >...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Sorry for the delay, been a bit tied up entertaining a baby!!
I have managed to fix my port 443 issue, so have deployed without any modification, and all is working.
I wasn’t able to get it working on a different port, but I guess this is a bit of an edge case anyway.
FYI - 1. verified from my phone, user and password correct and could reach the REST api, 2. valid cert in place, verified with 1, 3. using same settings as now working config (other than changing back to port 443.
So, I either did something wrong, or it is not possible to use a none standard port.
I’ll close this as I’m back up and running now on port 443.
Thank anyway.
@jmccoy555 were you able to resolve your issue? If so, can this issue be closed?