Password Protected User Can Log In Without Password (Docker)

[BAlGaInTl 279]

So I tried to recreate this on my beta install, and I just couldn't do it.  I tried to recreate the settings as you described them. 

 

So your Emby (and Bitwarden) install is reporting "localhost" (127.0.0.1) as the IP for everything?

 

What happens if you manually populate the local IP address in your Emby config?  

 

I even spun up a new reverse proxy (Nginx) and basically left all of the defaults.  Here is that config as reported by Nginx Proxy Manager:

{
  "domain_names": [
    "beta.domain.net"
  ],
  "forward_scheme": "http",
  "forward_host": "192.168.0.2",
  "forward_port": 8096,
  "access_list_id": 0,
  "certificate_id": 1,
  "advanced_config": "",
  "locations": [],
  "block_exploits": false,
  "caching_enabled": false,
  "allow_websocket_upgrade": false,
  "http2_support": false,
  "hsts_enabled": false,
  "hsts_subdomains": false,
  "ssl_forced": false,
  "owner_user_id": 1,
  "meta": {}
}

Not sure if that helps or not.

 

If your proxy isn't passing the correct information, then Emby wouldn't know what the IP is.

[a1pilot 2]

Spent several hours testing. It's not the docker issue. This is reporting localhost, but the docker issue reports the container IP.

 

Spun up a new VM to replicate and it didn't have the issue - despite having direct copies of the config.

 

Did a fresh setup and the issue hasn't reappeared.

 

The logs shows I had an update to PHP and Apache where the configs were updated, so I'm doing a diff compare with the current ones to see if anything in there may be causing issues.

 

Good: not linked to Docker, so not an easy to occur issue.

Bad (for me): unknown cause.

[BAlGaInTl 279]

Spent several hours testing. It's not the docker issue. This is reporting localhost, but the docker issue reports the container IP.

 

Spun up a new VM to replicate and it didn't have the issue - despite having direct copies of the config.

 

Did a fresh setup and the issue hasn't reappeared.

 

The logs shows I had an update to PHP and Apache where the configs were updated, so I'm doing a diff compare with the current ones to see if anything in there may be causing issues.

 

Good: not linked to Docker, so not an easy to occur issue.

Bad (for me): unknown cause.

 

Regardless of the reason, I'm glad that you got it working.