aptalca

You guys need to use container ports of apps, not host ports

I'm not sure what import folder you are referring to, but you can upload books through the web interface. That is the correct method. However, the location the books reside in has to be accessible by the container, meaning you don't upload through the web, but you use the web to point to the books calibre should import. Calibre-web is a separate app by a separate developer. It is simply an alternative web interface for calibre and it requires an existing calibre db to connect to. This image only replaces the RDP Calibre image that is in my personal repo. This one is more up to date and will continue getting updates whereas the RDP Calibre will be deprecated once I write migration instructions for existing users.

I'll look into creating a "development" tag for their beta releases. It looks like they release them on a sensible schedule.

You'll have to wait. 1.33 is the latest stable version: https://github.com/cdr/code-server/releases

You need to uncomment it (remove the # sign)

Don't mess with mapping folders in those locations. To test, just edit the crontab file under your config folder and restart the container. Make sure you have more than 1 minute between your upcoming script run time and restarting the container.

Try this: https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

That's a new one for me. Check that file /config/etc/letsencrypt/renewal/website.com.conf to make sure it contains all the parameters including this line: dns_cloudflare_credentials = /config/dns-conf/cloudflare.ini

For future reference and other users, you don't need to install nano inside the container as you can edit the file on the host under the mapped config folder

Yes, that should work. I believe I had done just that a while back.

It's simple, just use one of the examples from the default site config and plug in your IIS server's IP and port

Stream module is already installed and enabled. I use it to proxy vpn tcp connections

We need more info than "not connecting" Is this a new container or existing? What address are you going to? What is the docker run command?

Update: this was solved on discord. Pihole / dns settings were preventing outgoing connection to letsencrypt servers

RTFM is universal; applies to people of all ages, genders and medical conditions.

Then you enabled http auth in heimdall. Don't enable it in letsencrypt. Doubling up will cause issues.

Or you could have read the instructions in the readme, which talks about renewals. We do not support running manual commands inside the container. You're on your own from this point on

Do you have htpasswd file in both letsencrypt and heimdall? If so, delete the one in heimdall. If not, clarify what you're doing. It's not clear where you're running the htpasswd command and where you're deleting the default file.

Host networking doesn't work on the latest unraid. Plenty of posts in this thread if you search. Use bridge networking

We do not support users running manual commands. The readme contains info on how to troubleshoot renewal issues. In your case, either your ip on duckdns is wrong or your port isn't forwarded properly

The server is already claimed by an account, you can't expect to just claim it by another. Try removing it from the old account first

https://github.com/linuxserver/docker-openvpn-as/blob/master/README.md#application-setup

Comment out the main location block in the default site config

Depends on if they made the file available at the same endpoint. It may work, worth a try, but you need to use the long version with all the extra digits after the dash

That's likely the macvlan security feature that blocks connections between host and macvlan containers