Web Installation Issues

[John]

Hello,

I am having issues installing the web app. Right now, even after following all the steps outlined at https://github.com/nutechsoftware/alarmdecoder-webapp, I am still only getting the default nginx welcome page.

I had to make some directories for the copy commands to work, as well as follow https://github.com/nutechsoftware/alarm ... /issues/10.

What files do I need to show you here in order for you to diagnose my problem?

Thank you very much!
John

[kevin]

Make sure the default website in /etc/nginx/sites-enabled/ is disabled and only the alarmdecoder config is enabled

[John]

Make sure the default website in /etc/nginx/sites-enabled/ is disabled and only the alarmdecoder config is enabled

Hi Kevin,

Thanks for the quick response!

Code: Select all

user@Ubuntu1604:/etc/nginx/sites-enabled$ ls
alarmdecoder


Looks like the default config is removed, and the only config remaining is the AlarmDecoder config.

Still getting the default nginx screen.

Thanks for your help.
John

[kevin]

Very strange. Can you look at the nginx logs in /var/log/nginx/ to see if there is anything pertinent?

Can you bypass the proxy and access the webapp directly (http://alarmdecoder.local:5000 by default)?

Did you make sure to restart nginx after putting the alarmdecoder config in place?

The only reason I can think of nginx serving the default page in this instance is if it is somehow cached.

[John]

Very strange. Can you look at the nginx logs in /var/log/nginx/ to see if there is anything pertinent?

Can you bypass the proxy and access the webapp directly (http://alarmdecoder.local:5000 by default)?

Did you make sure to restart nginx after putting the alarmdecoder config in place?

The only reason I can think of nginx serving the default page in this instance is if it is somehow cached.

Nothing interesting in the logs.
I can not access it via port 5000. (Connection refused)
Not sure why it would be cached, but I tried on multiple devices with the same result.

I've tried installing on multiple boxes, maybe something changed in Ubuntu, and now it is not working?

[kevin]

Can definitely say that we have not tested on ubuntu 16.04.

If it is not listening on port 5000 that means the gunicorn worker is also not running or listening properly.

Please verify your nginx and gunicorn versions - also check the gunicorn logs in /var/log/gunicorn.d/*.log as well as any alarmdecoder logs in /opt/alarmdecoder-webapp/instance/logs/

I am unsure which versions of these packages ship with Ubuntu 16.04, but we do provide build instructions for a specific version of nginx for sure.

[John]

I have decided to use my raspi for this project. It is working out very well.