Shlink behind Nginx reverse proxy

[akaii78]

Hi Guys,

What is wrong with my config?

I'm using Nginx reverse proxy here is the conf :

server {
        listen   80;
        server_name    www.lien.com lien.com;
        return 301 https://www.lien.com$request_uri;
}
server {
    listen 443 ssl;
    ssl on;
    ssl_certificate /etc/letsencrypt/live/www.lien.com/fullchain.pem; # managed by Certbot               │
    ssl_certificate_key /etc/letsencrypt/live/www.lien.com/privkey.pem; # managed by Certbot
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

    server_name  www.lien.com lien.com;
    charset utf-8;
    set $upstream 192.168.8.10;
    location / {
        proxy_pass http://$upstream;
        proxy_set_header Host $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;
        proxy_read_timeout 90s;
    }
}

And for Shlink I'm using also Nginx here is the conf :

server {
    listen   80;
    server_name    192.168.8.10;
    index index.php index.html index.htm index.nginx-debian.html;
    error_log /var/log/nginx/lien.error.log;
    access_log /var/log/nginx/lien.access.log;
        root /var/www/html/shlink/public;

        location / {
                # try to serve file directly, fallback to app.php
                try_files $uri /index.php$is_args$args;
        }

        rewrite ^/(vendor|translations|build)/.* /index.php break;
        location ~ \.php$ {
                fastcgi_split_path_info ^(.+\.php)(/.+)$;
                fastcgi_pass unix:/var/run/php/php8.0-fpm.sock;
                fastcgi_index index.php;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                include fastcgi_params;
        }
}

When I try to activate the server I get this error message :

Oops! Could not connect to this Shlink server.
Make sure you have internet connection, and the server is properly configured and on-line.

Thanks for your help guys, I'm stuck !
akaii

[benhartwich]

I am having the same issue after updating from 3.1.1 to 3.3.0. It seems that there is something broken now. I´ve also added cors header manually to nginx, but it doesn´t work. Also a downgrade seems not possible.

[acelaya]

Please, try not to jump into premature conclusions, as most probably the fact that you use a reverse proxy is not relevant in your case and will only confuse others.

Have you tried accessing your instance without the proxy? Does it work from the command line? Have you checked the logs to see if there's any new error that appears too frequently?