ThatBrownGuy35
-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ThatBrownGuy35
-
-
Yup; just did it again. Sorry, is there any additional information I can provide you with?
-
I'm having a weird issue where my Plex is not able to communicate outside my network and I am unable to claim the server. I get the following warnings in my logs:
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
socket() failed: Address family not supported by protocol
Failed to create IPv6 socket, proceeding in IPv4 only mode
socket() failed: Address family not supported by protocol
Plex is running as a host and is using public port 32400.
It was running perfectly fine until a recent update. Any help would be much appreciated!
Don't know what the issue is, but that error message is harmless and I see it on my install and if you look at the log the poster above you attached it's also there too. Try stopping the container, deleteing Preferences.xml and restarting the container.
Going through this thread I found users who were having a similar issue and have already tried deleting preferences.xml; Plex is unable to attain a private IP.
-
I'm having a weird issue where my Plex is not able to communicate outside my network and I am unable to claim the server. I get the following warnings in my logs:
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
socket() failed: Address family not supported by protocol
Failed to create IPv6 socket, proceeding in IPv4 only mode
socket() failed: Address family not supported by protocol
Plex is running as a host and is using public port 32400.
It was running perfectly fine until a recent update. Any help would be much appreciated!
-
Not that I have any clue about this container or its setup, but host port 80 is definitely already in use (by unRaid's emhttp) unless you've changed the port unRaid operates on.
that was it, i'm a big dumb dumb. thanks!
-
Hey, so I'm trying to get Nginx-LetsEncrypt set up but it refuses to start if the Network type is set to Bridge. No logs are generated. Starts if Network type is set to Host or None but the logs say that Nginx has failed. Any ideas?
Thanks in advance
Post a screenshot of your settings and the docker log please
Are you sure that the ports you are trying to forward in bridge mode not used for anything else?
Ports arnt being being used for anything else. No logs are generated when in Bridge mode
-
Hey, so I'm trying to get Nginx-LetsEncrypt set up but it refuses to start if the Network type is set to Bridge. No logs are generated. Starts if Network type is set to Host or None but the logs say that Nginx has failed. Any ideas?
Thanks in advance
[Support] Linuxserver.io - Nextcloud
in Docker Containers
Posted
Hi guys,
So I went to install Nextcloud yesterday using CHBMB's walk through but i'm running into an odd error, nextcloud wont properly run, no WebUI shows up; I went through the forum but I didn't see anyone with a similar issue, here are my logs
tar: /tmp/nextcloud.tar.bz2: Cannot open: No such file or directory tar: Error is not recoverable: exiting now [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... cp: cannot create regular file '/config/www/nextcloud/config/config.php': No such file or directory chown: cannot access '/config/www/nextcloud/config/config.php': No such file or directory [cont-init.d] 60-memcache: exited 1. [cont-init.d] done. [services.d] starting services [services.d] done. Could not open input file: /config/www/nextcloud/cron.phpNextcloud is on port 444 & the AppData config on disk1 since i do not have a cashe drive. Any help would be appreciated.