Liquidbings

Not at exactly the same time but around then yes...Thinking about it it may have been after a restart happened so whatever got messed up might have been at the time of changing some of the ports etc on those containers but not actually implemented until the restart took place I just removed those 2 dockers via command line and am rebooting to see if that has any effect Edit: Well that did nothing still not able to access still same issue in log But no welcome to our web server messages now

I did have a few containers setup to use a reverse proxy that had stopped working around 6.9.1 that I had been toying around with recently trying to get working again, Swag, ombi I changed a few settings in pihole and swag within the last few days attempting to make swag work

Complex bonding has been there since the server was built. Its just the 2 gig ports bonded and has been working fine. I have gotten that warning many times with no issues. The Ip has been always set by to 192.168.1.25 by mac address in the router and I am definitely trying to go directly to that address. Looking through the log with my severe lack of knowledge, would nginx not being able to start because of things already on the port be possibly causing some of the issues?

Couldn't figure out how to get it without being able to download through the gui but found it through the flash drive. towerx2-diagnostics-20210921-1756.zip

One would think this but I can see the ip address of the server in my router which I have manually configured months ago and im going right to that ip... Also I had been using this same method for months now and use a bookmark so nothing changed there either...Im baffled I can access all my files via network on windows still without issues

So the other evening I had a weird issue, I could no longer access the server via My Usual method 192.168.1.xx. Which up until that evening had been working fine. I finally was able to access the server via, "Towerx2/login" for some odd reason. This method had been unworking up until this happened. Then all of a sudden today I am unable to access the server via either of those methods. I can still access via monitor and keyboard hooked up to server but gui seems to be not working with this method as well. Sometimes Im getting this when I try and login and sometimes nothing at all Welcome to our server The website is currently being setup under this address. For help and support, please contact: me@example.com

Ok so after some more investigating on my end I tried making another liquidnet with all lowercase and reinstalling the swag container started getting a different error this time around. "Docker: Error response from daemon: driver failed programming external connectivity on endpoint swag (642dd79e56b00d7ad807afeff98f2501afb16cdebe19a2666ed63a74bb2dbe11): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use." So I did a netstat lookup on 80 and it shows nginx and nginx workers on there. I wasn't sure if this something that may be causing an issue or is it something I'm unfamiliar with and normal?

I tried making another one and using that and I got the same error. Would it be be better to recreate the original or would this accomplish the same thing? The networks show up correctly from the dropdown in edit container. and when I list the networks in terminal they show up as what appears to me to be correct # docker network inspect Liquidnet [ { "Name": "Liquidnet", "Id": "edited out", "Created": "2021-07-17T17:10:47.916206832-04:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.18.0.0/16", "Gateway": "172.18.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} } ] Thank you for such a quick reply as always

Does anyone have a way to fix my containers not being able to use custom network any longer after upgrading? It started with 6.9 but still isnt fixed for me in 6.10. I just get "No such container" error if I click start on anything that uses a a custom network And the error when applying custom network while editing the container is "docker: Error response from daemon: network Mynet not found. The command failed." I had custom networks working for over a year now after following spaceinvaderones video and just cannot figure out what happened or how to fix it. towerx2-diagnostics-20210912-1216.zip

Thank you all for alll the help. This post helped me fix my issue. I had to add the adresses/full subnet to the ignored line as the checkbox failed to do its job... Quick fix that just required some deep digging to sort out. What a pain in the pooper lol Thanks everyone for being such a wonderful source of info! ❤️

Really appreciate these game servers! I'm having trouble accessing the terraria server from outside the local network. I can connect on the local ip but when friends try to connect from outside the house it never even shows in the logs. I've added the port into the port forwarder on the router. I tried adding the ip into the config file and didnt seem to help. Also tried adding steam and or lobby lines in and neither of those seemed to do anything for me either. Feel like its something simple I'm missing. I poked through the pages here and didn't see any relevant info. Thanks for any help anyone might be able to provide.

Flubster fixed worked like a charm and thanks to sloppy I was able to get through it no prob! Woke up to the issue and within 20 mins had it fixed thanks to all of your support! Couldn't do it without yall and hope everyone is doing well in these weird and crazy times. Your support is appreciated more than ever! ❤️

Thank you kindly for the quick reply. That seems to correlate to what I see. The Check starts to run at 12:30 and 13/15 of those errors were within 18 seconds of that and the other 2/15 were within 6 hours of a 23 hour run. I will likely run another check and see what comes up the second time to be safe.

Howdy folks, Just wanted to say hi and introduce myself to this wonderful community! Been loving UnRaid and everything that goes with it! Yesterday the monthly parity check ran and came up with 15 sync errors. From everything I've read and deciphered so far it seems this can be normal if there have been any dirty shutdowns, and I believe there may have been 1 or 2 during a couple bad storms we had. (on a side note if anyone could recommend a good UPS for my system lol). The thing I could find in the logs that looked related was this bit I thought I should maybe post the logs here and see what you guys thought as I have no idea really and am still learning the ropes. Thank you kindly for any and all help you may be able to provide. towerx2-diagnostics-20191104-1137.zip

Hello and thank you for such a wonderful OS. Couldn't be happier with my experience so far. I tried to make the upgrade the other day to full license key. After 24 hours I contacted support. I have not heard back and figured this would be the next best step. I assume it may just be that its the weekend but just to be safe I thought I would post here. Invoice No.: 56257 Order No.: 498176734 Date: 09/06/2019 Thank you kindly for any and all help you may be able to provide.