Roxedus

Did you actually enable the DHCP scope? it doesnt listen before there is a enabled DHCP scope.

You cannot "change" port when running in host networking

I have no idea how to do that on NPM, you might have some luck with adding some headers with the advanced settings for the location. We have a article on this problem in our docs. This what you should add: proxy_buffer_size 128k; proxy_buffers 4 256k; proxy_busy_buffers_size 256k;

Depending on how you set it up. The last guide I saw needed you to change the hostname/forward ip, on the auth location.

This can be expanded to use apprise as a notifying agent.

@Jomo Did you get the new auth location going? the sample in swag should be updated

Do you have the latest image?

NOTE: You exposed your plex token, you should revoke all logged in sessions in plex to generate new ones The snippet doesnt seem to have any attempts to use the auth

And you restarted SWAG, and still got that 500 error? Paste nginx logs

Is Organizr running? I assume it works hitting organizr itself?

You need to update the organizr-auth file in swag

https://docs.organizr.app/books/setup-features/page/organizr-20-->-21-migration-guide#bkmrk-nginx-auth_request

Did you change the mapped port, or did you use the default mapped port of 9876?

Changed how? the \ needs to be there, because they are escape-characters. the config becomes malformed without it

Its purely a cli based container, and opted not to add in the recent linuxserver template push

I created this for my own sanity a while back. https://selfhosters.net/docker/templating/templating/#0-enabling-template-authoring-mode

You do not need fail2ban, it is nice to have though.

Go back to the local adress with /admin after entering the token, it did actually auth.

502 means nginx cant talk to the container.

@CorneliousJD Unfortunately doing a switch isn't that easy, template wise. The best approach would be to create a separate template for the new image to not break existing installs, and have fix common problems tell users to switch. I will do the first part now.

@WeAreTheDynamite I would reach out to the project itself, as I cant see anything obvious either. https://github.com/dani-garcia/bitwarden_rs

You can delete the default action, of you define it in your jails, yes

So the regex is working, the only thing is that f2b doesn't start

Test the failregex on the command line fail2ban-regex /bitwarden/bitwarden.log /config/fail2ban/filter.d/bitwardenrs.local

Ok, that logline indicates that f2b doesnt start afaik. I dont have any default banaction, but i imagine defining the same action twice isnt optimal