Repetier-Server with ngnix reverse proxy show a blank welcome page

rosariopagano

Hi,

I followed the link https://www.repetier-server.com/webserver-access-repetier-server/ to add a reverse proxy for accessing RepetierServer by https.

Installation and configuration of nginx was ok but when I try to go to https://<myIP>; I see only the RepetierServer welcome Page with no user identification.

Just a blank Page with, on top, a blu line with the RepetierServer icon, version label and following icons: home, fullscreen, config, and language.

No way to go over.

there is some other think I need to do?

rosariopagano

Just to complete info. I'm using an RPi 2 (raspbian 7.1) wich install tje nginx 1.2.1 version.

Regards
Rosario

Repetier

The documentation was for Jessie (8.0). You need websocket support and that was introduced only with nginx 1.3. Alternatively compile yourself a more up to date nginx version.

rosariopagano

hi,

ok.  I'll try soon.

Thanks

Repetier

Just install the V3 image that should appear tomorrow and everything should be fine.

rosariopagano

Hi,

I installed latest nginx version:

root@raspberrypi:~# nginx -v

nginx version: nginx/1.9.12

I did all steps but I still can't see login. In firefox logs I see websocket connection failed.

I'm working again on it.

rosariopagano

rosariopagano said:

Hi,

I installed latest nginx version:

root@raspberrypi:~# nginx -v

nginx version: nginx/1.9.12

I did all steps but I still can't see login. In firefox logs I see websocket connection failed.

I'm working again on it.

I solved. Restarting nginx. May be something goes wrong previous start.

So now, just to ask if you can say any suggestion, my office network works with a proxy. 

May be the proxy close websocket?

Thanks in any case

Rosario

rosariopagano

This is the erro I can see in firefox console:

WebSocket connection to 'wss://217.133.133.42/socket/?lang=it' failed: Error in connection establishment: net::ERR_SOCKS_CONNECTION_FAILED

Repetier

So what is the state now. You have nginx as local proxy and locally it works but from remote you get this error?

wss means you are using https for viewing the webpage. If you are using a self made certificate that could be a problem if one of the components does not trust it. html shows a warning page I think, but wss will probably just fail in that case. You would need to import the certificate I guess.

BlackChart

I have this excact problem.

# cat /etc/debian_version
8.6

# nginx -v
nginx version: nginx/1.6.2

# vim /etc/nginx/sites-available/proxy

#Repetier / CNC / 3D
server {
        server_name hidden.to.public;
        listen 80;
        client_max_body_size 1000m;

        location / {
                proxy_pass http://192.168.1.254:3344/;
        }
        location /socket/ {
                proxy_pass http://127.0.0.1:3344/socket/;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
                proxy_read_timeout 86400;
        }
        # printer frontend does not require password, so we forbid it from external
        location /mod/front/ {
                deny all;
        }
        location /modules/front2/ {
                deny all;
        }
}

I have tried restarting nginx several times.

Anyone have any idea?

Repetier

Does it work without nginx directly on port 3344?

I had a user saying it does not work if you have no supported language defined in your browser. In that case add ?lang=en to the url and it should work.

BlackChart

Yes - directly to port 3344 it Works like a charm.

When doing debugging in Chrome, I can see i tries to open ?lang=en but get 502 bad gateway response

BlackChart

Sorry - never mind *DOH*

Perhaps I shall write myself a note NOT to try something like this when in need of sleep

It was a misspelling in the server config.

See above. / get redirected to 192.168.1.254 and /socket goes to 127.0.0.1 when they both actually was supposed to go to 192.168.1.254.

rosariopagano

I configured nginx as described and accessinng it through a https connection works perfectly. I just need to use latest version.

Also pointing it when I'm in my office (browser have an http proxy configured) I can see my printer server.
May be I had problem in my first connection due to cache/certificate.
next day I was in my office all worked fine without any change.