@nichwall commented on GitHub (Jan 9, 2025):
Could this be achieved by having different browser profiles? Like do your users individually have multiple accounts or just share a computer/browser?
@k3davis commented on GitHub (Jan 9, 2025):
@nichwall fair question; in our case (young family) there's a central shared computer logged in as one user and ABS is installed as an "app" so the…
@mikiher commented on GitHub (Jan 11, 2025):
Actually, looking at the code, it's not using req.host, but rather req.get('host'), (equivalent to req.headers.host) which should not suffer…
@andrewinmoco commented on GitHub (Jan 12, 2025):
@mikiher:
Before I share the screenshots I noticed something interesting:
I run audiobookshelf on docker (HTTP on port 13378). I use a…
@mikiher commented on GitHub (Jan 12, 2025):
Thanks for the response.
I suspect ngnix is stripping the port from the original request's Host header.
Can you please share your ngnix config…
@andrewinmoco commented on GitHub (Jan 12, 2025):
@mikiher
`proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_…
@advplyr commented on GitHub (Jan 12, 2025):
Ah great, thanks for figuring that out. We can close this out
@mikiher commented on GitHub (Jan 12, 2025):
This was actually useful.
We actually recommend using proxy_set_header Host $host for nginx configuration in our documentation. Usually it…
@advplyr commented on GitHub (Jan 12, 2025):
Yeah that makes sense
@advplyr commented on GitHub (Jan 8, 2025):
I see that this is a bug with express stripping the port. It doesn't strip the port number in all cases though so I haven't reproduced the issue.
htt…
@advplyr commented on GitHub (Jan 7, 2025):
Related https://github.com/advplyr/audiobookshelf/issues/711
@mikiher commented on GitHub (Jan 7, 2025):
I just verified that this only happens with cutting edge source (I reverted to v2.17.7 and could not repro).
@mikiher commented on GitHub (Jan 11, 2025):
I'll look at this. Maybe we can work around this. It would be also good switch to express 5.
@github-actions[bot] commented on GitHub (Jan 20, 2025):
Fixed in v2.18.0.