Server Version#: Ubuntu Server 20.04 LTS
PLEX Server Version#: 1.24.5.5173
Player Version#: 4.68.0
Plex Media Server.log (64 KB)
I cannot claim my server and I am having a difficult time finding the issue. Server worked great without issues before moving, I am using a BGW210 Router provided by my ISP and trying to determine if that is my issue before trying anything else. I have purged and uninstalled my Plex server multiple times now without any change. Fails to claim at both the basic setup from localhost and when attempting to claim it from settings. Getting close to just hosing my ubuntu server install in frustration as this is the primary purpose of this headless server, just trying to save the aggravation of OS install or redesign of my home network.
Log shows no claiming attempt, and roll over with every restart.
So please reproduce, and then upload a zip with all the PMS log files.
Plex Log.zip (348.2 KB)
Weird…So new issue it seems i get an error when attempting to download logs through the webapp (server is headless). I pulled the directory through my console though, and packaged a zip myself thanks for quick response.
Maybe a DNS, FW or default router issue?
From the log:
ERROR - Error issuing curl_easy_perform(handle): 7
Oct 29, 2021 17:26:35.638 [0x7fb924eebb38] WARN - HTTP error requesting GET https://plex.tv/users/feef3bb69ede900b/avatar?c=1635542964 (7, Couldn't connect to server) (Failed to connect to plex.tv port 443: Host is unreachable)
Yes I saw this too, and is what made me look toward router. Router doesn’t offer a custom DNS it seems…any idea of a workaround? Gonna attempt shutting of FW. Trying to put off the slog of setting up another router with this clunky brick my ISP gave me.
No idea, since not knowing your router nor ISP
But if the router allows clients to ask DNS requests to the internet, configure your OS to use Google instead
8.8.8.8 and 8.8.4.4
Yes seems its a rabbit hole of settings for this router. I was in process of setting it to using googles DNS when I discovered I cant change DNS settings. Ill report back in a bit, gonna try and neuter this wacky router ATT provided me with, and place a better one behind it that I am familiar with as that will probably faster than trying to decipher this thing and make it work for me, thanks for nudge in right direction though. At least I am not doing OS install then realizing this too.
Just curious here, what’s the name of your ISP?
AT&T its DSL. *
Leaseweb USA, Inc.
Ok not sure what I did here, found a couple configuration issues with new router. What was messing me up was I had internet access this whole time on server somehow but GW wasn’t configured like my last place. So I hadn’t thought to dig into it right away. That mixed with network and server restarts seems to somehow got it working. Appreciate the help, I will try not to breath on it now.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
