Domoticz webpage not completely visible from the internet

[EelkoL]

I've got a strange problem:

I just set up Domoticz on a raspberry pi, and added forecast.io, next week I will get a smart meter and connect that too.
I can connect from my internal network to the domoticz page on port 8080.

However, when I enable a port-forwarding rule in my router (a ziggo ubee modem), so that from every address (0.0.0.0), port 8080 request is forwarded to port 8080 on my Pi, the web-page only works partly?!?

I connect from a browser at the office to my public IP adress, port 8080, I get a page with the background of the domoticz web page and a drop down box in the upper left corner that is empty. When I move my mouse over the drop-down box, it says "replace device".
I already tried disabling the firewall of the router, forward all ports to the IP-address of the PI, enable and disable authentication, IE and chrome...

I do not get it!

The screenshot is this:

[nayr]

whats the console log say in Chrome? VIEW -> Developer -> JavaScript Console.

[EelkoL]

I didn't even know there was such a thing..
The java console says:
Creating Application Cache with manifest http://myname-hidden.ddns.net:8080/html5.appcache
(index):1 Application Cache Checking event
(index):1 Application Cache Downloading event
(index):1 Application Cache Progress event (0 of 532) http://myname-hidden.ddns.net:8080/css/images/img08.jpg
(index):1 Application Cache Progress event (1 of 532) http://myname-hidden.ddns.net:8080/images/next.png
http://myname-hidden.ddns.net:8080/js/j ... 1.3.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
(index):1 Application Cache Progress event (2 of 532) http://myname-hidden.ddns.net:8080/views/dpfibaro.html
(index):1 Application Cache Progress event (3 of 532) http://myname-hidden.ddns.net:8080/css/remote.css
(index):1 Application Cache Progress event (4 of 532) http://myname-hidden.ddns.net:8080/css/ ... 56x240.png
(index):1 Application Cache Progress event (5 of 532) http://myname-hidden.ddns.net:8080/images/scale.png
(index):1 Application Cache Progress event (6 of 532) http://myname-hidden.ddns.net:8080/secp ... igital.eot
(index):1 Application Cache Progress event (7 of 532) http://myname-hidden.ddns.net:8080/imag ... ection.png
(index):1 Application Cache Progress event (8 of 532) http://myname-hidden.ddns.net:8080/imag ... 48open.png
(index):1 Application Cache Progress event (9 of 532) http://myname-hidden.ddns.net:8080/images/blinds48.png
http://myname-hidden.ddns.net:8080/js/i ... 8.0.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
(index):1 Application Cache Progress event (10 of 532) http://myname-hidden.ddns.net:8080/css/ ... -Light.eot
(index):1 Application Cache Progress event (11 of 532) http://myname-hidden.ddns.net:8080/imag ... Window.png
(index):1 Application Cache Progress event (12 of 532) http://myname-hidden.ddns.net:8080/i18n ... cz-sl.json
(index):1 Application Cache Error event: Resource fetch failed (0) http://myname-hidden.ddns.net:8080/i18n ... cz-sl.json
http://myname-hidden.ddns.net:8080/js/bootstrap.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/bootbox.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/jquery-ui.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/j ... nch.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/j ... ect.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/j ... ick.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/colpick.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/n ... ry.noty.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/n ... uts/top.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/n ... topLeft.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/n ... opRight.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/n ... default.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/j ... les.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/ZeroClipboard.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/d ... ols.min.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/date.format.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/highcharts.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/h ... ts-more.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/m ... porting.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/export-csv.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/t ... rk-blue.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/domoticz.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/d ... devices.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/j ... r-addon.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
http://myname-hidden.ddns.net:8080/js/require.js Failed to load resource: net::ERR_CONTENT_DECODING_FAILED
(index):217 Uncaught ReferenceError: $ is not defined
(index):509 Uncaught ReferenceError: load_cam_video is not defined

[nayr]

it looks like your work has a transparent proxy thats mucking with the compression.. I think thats why your getting content_decoding_failed from work and not from home. Its pretty common they do it for logging web activity of employees.

might try using HTTPS, that typically will stop this from happening.

[EelkoL]

Must be something else, as a colleague has exactly the same setup and it is working for him... Also when I try via mobile on 4G, it doesn't work.

I like the HTTPS suggestion, will try that and come back here...

[EelkoL]

I tried https on port 443, it actually works. So now can access the domoticz webpage from outside my local network, great!

[nayr]

A proxy would not mess with a "weird" port like 8080. If the company uses a proxy it will more likely block that port completely

weird port huh? lets try that theory out:

Code: Select all

$ cat /etc/services |grep 8080
http-alt	8080/tcp	webcache	# WWW caching service

nope, thats specifically a port many transparent proxy's will catch.. as many proxies listen on the same port number when they are not transparent.. Its actually designated as the alternate port to http/80.

Its also possible your ISP is running a proxy for caching purposes that was causing interference, alot of ISP's block residential hosting on port 80 entirely, others allow it but filter it for malware/abuse.. either way glad it works on HTTPS.. your better off using encryption.

What made me be suspect of a transparent proxy interfering was the fact that all the statically compressed files were the only ones throwing decoding errors.. as a network engineer I seen this many times when proxies compress an already compressed file.. typically the proxy will just strip the compression headers from your traffic and use its own headers and compression, it presumes its got the bigger pipe and for performance reasons it would rather not have to deal with compressed traffic coming in, so it requests no compression upstream, but these files are already statically gzip'd so they are coming back compressed regardless what HTTP headers are sent and the proxy blindly is recompressing them again.. resulting in a file your browser cant figure out to decode.

I suspect if you had un-gzip'd all the files in www/js it would have worked for you on this network.. but screw that, https was a better fix.

[EelkoL]

What do you expect to happen on other ports than 8080 for http? will the proxy interfere as well?
Just curious, I will leave it on https anyway..

[EelkoL]

By the way, I still think my personal modem/router/firewall is causing the problems, not the corporate proxy, as I have the same problem via mobile and my colleague does not experience problems at all.

[SweetPants]

Take a look at http://www.domoticz.com/forum/viewtopic.php?f=6&t=10330

Edit: Fixed in latest beta