I've got overseerr working for a dozen or so other people, through a SWAG subdomain reverse proxy. But I have one person trying to use it, they get the sign in page but when they hit sign in it just spins forever. I'm not sure where to begin troubleshooting this as it works for me on wifi, cellular, and I see other people making requests so I know I set it up right.
#One specific user can't get past login screen
8 messages · Page 1 of 1 (latest)
alright I've got someone else to try it, they use edge on their phone and it does the same exact thing. But he tried firefox mobile and that worked. Any ideas how I can... make it work more universally?
Have you followed the docs re SWAG?
https://docs.overseerr.dev/extending-overseerr/reverse-proxy
either using the bundled conf file or creating a new "overseerr.subdomain.conf" with the info listed on the above link.
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name overseerr.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_app overseerr;
set $upstream_port 5055;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}
}
Yep I'm using one of swags sample confs, looks pretty identical to that ^
Notably it seems to fail in facebook messengers browser when you hit the link, but it works when I copy that link into chrome on my phone
I vaguely recall having issues with the FB messenger browser. I think possibly as it's not a "full browser" maybe it doesn't load properly or load pop-ups etc?
IIRC there's a setting in Facebook/messenger that lets you open links in your default browser of choice rather than FBmessenger one. Might be a feasible workaround for now?
Yeah I'm gonna tell him to try another browser. Although my buddy that was helping me test this said edge on his phone didn't work either