![]() ![]() ![]() Once I'd see that "listening on 8080" it would always work, not this time. I've had that happen a few times after restart, so I stopped and restarted while watching the log. Only noticed a half hour later that the webui hadn't reloaded. As I've done for months now, I mindlessly clicked update and expected nothing to go wrong. I was at work over a cloudflare tunnel happily upgrading my entire library to h265/1080p+ as I've done for a few long weeks when I noticed the update. I'm new to unraid/docker, only picked it up about three months ago. I have literally NO idea how that would of previously worked!, I have not touched iptables whatsoever in the latest release, so if it broken with the latest it should of been broken with the previous version, are you guys sure you didn't change your home network address space or introduce VLAN's into your network?.īizarre right? I'd have noticed the problem on initial install had it not worked. After correcting I can get to both containers web gui’s. Just as you, I had left that default on BOTH containers, it has worked for months but I guess something in the last update shook it loose, but incorrectly configured none the less. Hopefully I caught everything I should delete prior. I've attached my supervisord.log for completeness. New since today's update is the following entry:Įrror: argument "8080_qbittorrent" is wrong: invalid table ID ![]() NOTE: the current -script-security setting may allow this configuration to call user-defined scriptsĪssumed they were nothing to worry about. OpenVPN ignores -cipher for cipher negotiations.įile 'nf' is group or others accessible I find the following interesting entries in my supervisord.log from before and after:ĭEPRECATED OPTION: -cipher set to 'aes-128-cbc' but missing in -data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). This has "worked" up until today's update.Ĭhanging to the proper 192.168.0.0/24 resolves the issue. I've got hundreds of this entry in my supervisord.log. But I'll post what happened in case it helps Smonrad or anyone else.Īpparently, since I installed this docker a few months ago, I was using the wrong value in "Container Variable: LAN_NETWORK". Thanks wgstarks, that appears to be all the hint I needed, resolved. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |