hmoney007

Same issue here

This worked perfectly using the adminer container to drop the two tables. Thanks I still think a monolithic container including mariaDB would be nifty for ghost

Nginx is erroring out with this repeated in logs: nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-26/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-26/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) I woke up to backup/restore v2 completed and no containers/vms exposed. Figured out it was nginx which shit the bed and didnt come back up after backup. Backup simply kills all containers then backs them up then starts again, therefore no changes to my config took place. I tried rolling back to v 1.16.0 with no luck. There is no npm-26 anymore.. that was an old proxy host which is not used anymore. Please let me know what I should do to get this up again *EDIT* - I just went to the "live" folder and copied/pasted another proxy host folder and renamed as npm-26 and now it works. Seems like something is broken on the code side but this is a quick and dirty workaround.

Thanks for the detailed response. Yes I did attempt forcing the 4.0 branch but the errors from db were still present. I will do as you suggested and take a fresh backup of the db prior to attempting the fix and report back. I'll also take a look at your suggested replacements for mysql-workbench. On another note i am curious if there would be a major downside to baking mariadb into the container. I noticed my mariadb container uses like 30mb of ram and cpu sits at 0% usage with multiple containers writing to it. Either way, thanks again for the response!

I am not sure how to do that. I installed mysql-workbench but it doesnt seem to play nicely with mariadb. Also per the same suggesiton you are mentioning above, the revert to 4.0 was suggested *instead of* touching the database. It would be greatly appreciated if you would provide the command(s) needed to remove the index. edit: when i asked a friend to take a look he wondered if there was an issue with the container provided by you since it "upgrades the base image when pulling a new version". Is this something of concern?

I am having the same issues as others above with the lock file. Forcing it to use the 4.0 branch does not bring joy

The docker container vpn network support and the rebalance cache pool to different raid levels are both great to see!

That's awesome! I'll give it a whirl

Ah ok, I don't use irc that often and only on freenode. I just figured this would be better than using a bouncer.

Can I request that you add VPN functionality similar to your deluge and other baked-in vpn containers?

3 years later, are there any changes and/or additions to the VM settings available in unRAID's vm creation template that you'd suggest?

One of my biggest fears is my unRAID USB drive failing causing my entire system to go down. I'm wondering if there are any plans to allow for a secondary USB to be left in my unRAID machine and in the case of my boot drive failing, the secondary drive would become the primary with a notification in the gui of what happened.

I am unfamiliar with intrepid and incorrectly assumed it wasn't possible to build it on my own. The webui works fine, sure, but the whole reason i use this container and deluge GTK specifically is to be able to use my windows 10 vm to click magnet links and then have them download and live on my array.

I'm having the same issue and remote connections is enabled. I connect from a Windows computer, however the deluge website shows no plans for 2.x on mac nor windows... Are you able to duplicate this?

I apologize for not updating this. I was getting errors in the nginx proxy manager interface when trying to make changes to a new proxy host. I took a screenshot of my config, deleted the docker container + folder within appdata and then installed and configured it fresh. It's now working as expected! One thing I did notice: when adding multiple proxy hosts i went back to confirm that all of the settings were correct and noticed that almost all of my newly-configured proxy hosts had all of the options unchecked in the SSL tab, and I am 100% sure that I had checked them all off.

I updated nginxproxymanager last night and today I noticed that nextcloud wasn't connecting. I confirmed that my nslookups are still hitting my WAN IP, but none of my subdomains configured through nginxproxymanager are currently working. I did not change any configuration within the container. Is anyone else experiencing this?