[Bug]: Socket Failed to Connect - Swag & Unraid

[Borlean]

Describe the issue

UnRaid server using default community application template. When connecting locally via the IP address of my UnRaid server, everything works great.

However, once I try to go through my swag reverse proxy, with the below config from the readme, I am able to connect and login, but continually see a "Socket Failed to Connect" error. This happened on v2.0.1 and the new v2.0.2 version that was released a couple days ago.

  server {
    listen 443 ssl;
    listen [::]:443 ssl;
    
    server_name audiobookshelf.*;
    
    include /config/nginx/ssl.conf;

    location / {
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header Host $host;

      proxy_pass http://[IP of unRAID]:13378;

      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
    }
  }

I saw there was another issue thread on 'Socket Failed to Connect' that was focused on nginx proxy manager (#241 (comment)) and marked solved, but the socket error persists.

server {
  listen 443 ssl;
  listen [::]:443 ssl;

  server_name audiobookshelf.*;

  include /config/nginx/ssl.conf;

  location / {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

    proxy_http_version 1.1;

    proxy_pass http://[IP of unRAID]:13378;
    proxy_redirect http:// https://;

  }
}

Any ideas?

Steps to reproduce the issue

1. Any login from outside the network through swag reverse proxy.

Audiobookshelf version

2.0.3

How are you running audiobookshelf?

Docker

edit: changed version from 2.0.2 to 2.0.3.

[Borlean]

Marking as closed. Adblocker/FB Container on Firefox was causing the issue. Disabling those and everything works.