You don’t need to change the openHAB2 ports that are used by default (8080 for http, 8443 for https) when using a reverse proxy like nginx or apache.
The proxy is running on port 80.
The clients connect to the proxy on 80 and the proxy connects to OH2 on 8080.
Check the link on Benjy’s post on how to set up a reverse proxy:
If you want to use the upcoming Google’s stuff, you need to switch openHAB2 to listen to port 80 natively (no use of proxy).
This is more difficult since:
Kai, to share my experience: Traveling to Munich (I am not living in Germany) I took the chance to buy a Google home and trying it out at a friend who as an original Philips Hue. The procedure in the google home app had been still the same. Back home, google home stayed on hue-adapter.appspot.com and I was able to include my openhab! Thanks for all the support.
I don’t know if this is the correct place to put this information, but i just had to change the port on my first ever install of OpenHabian2… on Ubuntu 16.10… There was another service already on 8080…
I have installed the “unstable version” of the software, (for x10 support) and the server is now up, but it’s reporting the wrong port numbers into the log file…
Hi I’m very much a newbie to everything from programming to configurations, my start.bat of the version of OH2 as of about ten days (ie early Jan 2020) ago has Karaf as the webserver, and I’ve found that the port number can be changed in OpenHAB\runtime\bin\setenv.bat (using Win10, but the same should be true of other environments’ setenv files I guess) down around line# 86 or so. That’s worked for me, HTH.