Hi @Benjy, nope - it also says “bad gateway”. I can ping the Raspberry and I can connect through SSH, but currently I lost my web interface. I’m running a reverse proxy - could there be some flaw in the configuration after last nights update?
I’m not fully sure, but somehow I have the feeling, my nginx config got changed completel (/etc/nginx/nginx.conf)…
[Edit]: I found my configuration in the sites-enabled folder; so an altered nginx.conf doesn’t seem to be the problem
That’s odd, nginx shouldn’t be operating on port 8080. Would you be able to post the contents of the config in the site-enabled folder? Be sure to replace your domain with some placeholder.
Just noticed, I’m only operating using SSH - port 80 of my domain is shut down - and also http://[local ip]:8080 doesn’t work. Only https://[local ip]:443 works - whereas “works” means “502 bad gateway”
Here’s my config:
server {
listen 80;
server_name [name of my domain];
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
server_name [name of my domain];
ssl_certificate /etc/letsencrypt/live/[name of my domain]/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/[name of my domain]/privkey.pem;
add_header Strict-Transport-Security "max-age=31536000";
location / {
proxy_pass http://localhost:8080/;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
auth_basic "Username & password:";
auth_basic_user_file /etc/nginx/.htpasswd;
}
location /.well-known/acme-challenge/ {
root /var/www/[name of my domain];
}
location /doorcam {
proxy_pass http://192.168.1.81:35280/;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
As I said, I didn’t change anything in the config (for weeks now).
The last thing I can find in the openhab.log is from this morning where I made an update by using openhabian-config:
==> /var/log/openhab2/openhab.log <==
2018-05-02 08:43:18.455 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
2018-05-02 08:43:28.486 [INFO ] [lgtv.lginteraction.LgTvMessageReader] - Stopped LgTv Servlet
2018-05-02 08:43:28.490 [INFO ] [lgtv.lginteraction.LgTvMessageReader] - Stopped LgTv Servlet
2018-05-02 08:43:28.493 [INFO ] [lgtv.lginteraction.LgTvMessageReader] - Stopped LgTv Servlet
2018-05-02 08:43:28.572 [INFO ] [penhab.io.transport.mqtt.MqttService] - Stopping broker connection 'mqtt_broker'
2018-05-02 08:43:28.689 [INFO ] [io.openhabcloud.internal.CloudClient] - Shutting down openHAB Cloud service connection
2018-05-02 08:43:28.718 [INFO ] [io.openhabcloud.internal.CloudClient] - Disconnected from the openHAB Cloud service (UUID = eeae7573-2944-4e7f-adc5-94543ff9b69d, base URL = http://localhost:8080)
2018-05-02 08:43:28.872 [INFO ] [b.core.service.AbstractActiveService] - Exec Refresh Service has been shut down
2018-05-02 08:43:31.553 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Stopped Paper UI
2018-05-02 08:43:31.601 [INFO ] [.dashboard.internal.DashboardService] - Stopped Dashboard
Before we spend ages looking for a possible update error - is there a quick way to reinstall OH2-binaries (without losing the config)
Not a problem, your logs finish at saying that it’s stopped the dashboard (which is the web service), and it never restarts. If the process got stuck during the update, it’s best as you say to do a reinstall. first will make sure the process has stopped.
sudo systemctl stop openhab2
openhab-cli info
If the output still says:
openhab (Active Process 1393)
then we need to force kill the process.
kill -9 1393
Finally, reinstall openHAB2, keeping your configuration intact:
Glad to hear it! I’m guessing it was a very rare occurrence but if you come across the problem again then please let me know, and I’ll see if I can reproduce it.