aptalca

Letsencrypt renewal attempt logs are in the config folder

First, make a backup of your Plex data just in case (you can use the backup and restore plug-in) The image/container structure should be compatible. Stop the other container, then just create a new container with the linuxserver image and point the config folder to the same folder the other container was pointing to. That's really it.

"docker exec -it letsencrypt" is used to run things things inside the container while you're on the host console, outside of the container. If you're already inside the container, just run the part that starts with htpasswd

You're only supposed to rename the files, not move them to different folders. Documentation is pretty clear on that.

Your confs don't match your logs. The web address you're trying to connect to has http auth turned on. It looks like you have a conf somewhere that has an incorrect server name set (with /airsonic at the end), etc. Either go back to defaults and start over, it post your full config or it is impossible for us to help you

Define not working

Try incognito, 301 redirects are supposed to be permanent and are cached by the browser

Lua issues are harmless. Server name conflicts are a problem you need to fix. You likely have duplicate site configs

I believe you need to change the remote port shown on there

Make sure the container name is bitwarden and that both containers are in the same non-default bridge network

You can unselect the option for letting the client access other devices on the network. Put in the pihole ip into the dns ip setting in openvpn-as

Also, for anyone who's trying to troubleshoot ports. . . Can you see me only works if you already have a service that's listening on that port. If you have a cert error and you never get the "server ready" message in the log, there is nothing listening. Nginx is down because it doesn't start until certs are successfully retrieved. See here to troubleshoot: https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

Referring to the post I quoted. Your error literally says see the error message above but you didn't post the error message above.

See the error above

It auto updates itself weekly: https://github.com/alpinelinux/aports/blob/master/main/libmaxminddb/APKBUILD#L42

That command creates the credentials file. Then edit your site config files to enable it for whatever location you want

I don't even know what workspace files are. My workflow is, open terminal, go to workspace folder, git clone whatever, then from the top menu, open folder, select the cloned folder. Anything under the config folder is accessible by vscode. Also /config is the home of the user running vscode so things that vscode creates will likely be relative to that folder

Ah, I always turn off upnp on the router. Don't want some rogue apps opening ports to the outside without my knowledge

Post a full log and a screenshot of your container settings

None of the team members have a paid openvpn license so we can't really test how it works. I'll try to look into it, but I'm shooting in the dark here

Could be DNS issue (check IP), could be port forwarding (router setting looks correct as long as you moved unraid to a different port) or maybe your ISP just started blocking ports 80 and 443. See here to further troubleshoot (article not published yet but here's a preview): https://blog.linuxserver.io/p/3959a1d3-d70d-4d1d-a4ef-4dcdc0bcfd94/

After thinking about it, here's a PR with sudo access via an optional SUDO_PASSWORD variable: https://github.com/linuxserver/docker-code-server/pull/3

Use port 80 and tcp to connect

Root access in gui terminal is not very secure, the official container running as root is also not secure. If you want to add packages to this container and you want them to be persistent, use the custom scripts feature in our baseimages. Keep in mind that we cease to provide further support once you enable that so you will be on your own. Create a folder under /config called "custom-cont-init.d" and inside it place a file with "apt-get update && apt-get install -y blah" That script will be run on every container start and will survive container recreation Dev info here: https://github.com/linuxserver/docker-baseimage-ubuntu/blob/bionic/root/etc/cont-init.d/99-custom-scripts#L14-L31

I honestly have no idea what could cause the container to stop working. It literally just fires off a curl command every five minutes, driven by cron. Can you specify whether the curl is still firing?