# Stuck on "Not Authorized" after initial setup

**URL:** <https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243>\
**Category:** Plex Media Server\
**Tags:** server-linux\
**Created:** [November 12, 2024, 2:03pm UTC](https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243 "2024-11-12T14:03:52Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![fmer7](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@fmer7](https://forums.plex.tv/u/fmer7)\
**Post date:** [November 12, 2024, 2:03pm UTC](https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243/1 "2024-11-12T14:03:52Z")

</div>

Server Version#:1.41.1.9057-af5eaea7a  
Player Version#:  
\<If providing [server logs](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) please do NOT turn on verbose logging, only [debug logging](https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/#toc-1) should be enabled\>

I’ve setup a ProxMox container for my Plex server. I used the following instructions, which worked out great. [How to Install Plex on Proxmox (+ Hardware Acceleration)](https://www.wundertech.net/how-to-install-plex-on-proxmox/)

After step 7 “Configuring the Plex Application” I either get the “Not Authorized” screen or just a black screen with the Plex logo in the top right.

I’ve googled and tried various solutions with no effect. Most results seemed to be focused on widows or docker installs.

Additional details.  
I’m using PiHole for DNS and I’ve enabled local DNS for my hostnames.  
I have a 192.168.2.x network internally. The IP is static within the container.

LMK what other info would be of use.

---

<div class="post-metadata">

**Author:** ![dbirch](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@dbirch](https://forums.plex.tv/u/dbirch)\
**Post date:** [November 12, 2024, 2:15pm UTC](https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243/2 "2024-11-12T14:15:06Z")

</div>

Check the pihole logs for plex related blocked domains, and then post your [server logs](https://support.plex.tv/articles/200250417-plex-media-server-log-files/)

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [November 12, 2024, 3:47pm UTC](https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243/3 "2024-11-12T15:47:28Z")

</div>

you cannot use hostnames for initial claiming.

This is because PMS will see the hostname in the referred header and, no matter if local or remote, will deem the connection “remote”.

This is the root case of the “Not Authorized”

Solutions:

1. Connect to the server by LAN IP (must be same subnet)
2. Use a tool to help from inside the VM (e.g. tool below)

> **[GitHub - ChuckPa/UserCredentialReset: User Credential Reset utility for Plex](https://github.com/ChuckPa/UserCredentialReset)**
>
> User Credential Reset utility for Plex

---

<div class="post-metadata">

**Author:** ![fmer7](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@fmer7](https://forums.plex.tv/u/fmer7)\
**Post date:** [November 12, 2024, 4:02pm UTC](https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243/4 "2024-11-12T16:02:54Z")

</div>

Using my 192.168.2.x network to connect internally. I’ve also tried 127.0.0.1 using Lynx on the command line inside the CT.

I tried that script and it just spits out errors.  
Here’s the output.  
root@plex:~# ./UserCredentialReset.sh  
./UserCredentialReset.sh: line 7: DOCTYPE: command not found  
./UserCredentialReset.sh: line 8: html: command not found  
./UserCredentialReset.sh: line 11: data-color-mode=auto: command not found  
./UserCredentialReset.sh: line 12: data-a11y-animated-images=system: command not found

Apparently lines of code inside “{ }” are the issue? I removed a few in some lines as test bu then other errors pop up.

I installed shellcheck to troubleshoot. Got the following output

root@plex:~# shellcheck UserCredentialReset.sh

In UserCredentialReset.sh line 22:

 ^-- SC1009 (info): The mentioned syntax error was in this simple command. ^-- SC1073 (error): Couldn't parse this redirection. Fix to allow more checks. ^-- SC1072 (error): Fix any mentioned problems and try again.

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [November 12, 2024, 4:20pm UTC](https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243/5 "2024-11-12T16:20:38Z")

</div>

You didn’t download it correctly. You ended up downloading the github web text.

Go to github, let it show you the entire script.  
COPY that text into the browser.

Return the the Linux terminal window  
In a text editor (vi, nano, etc), paste the text, then save the script.

You’ll be able to see it’s clean script text

After exiting the editor, give it execute permission and then run it (as root)

Perhaps it’s better to download the tar.gz file (Releases) and then unpack it locally.

---

<div class="post-metadata">

**Author:** ![fmer7](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@fmer7](https://forums.plex.tv/u/fmer7)\
**Post date:** [November 12, 2024, 4:49pm UTC](https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243/6 "2024-11-12T16:49:34Z")

</div>

THANK YOU!!

This did the trick. Script ran properly to the end. I’m getting into the admin site, I’m adding my library and so far so good!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [February 10, 2025, 4:50pm UTC](https://forums.plex.tv/t/stuck-on-not-authorized-after-initial-setup/895243/7 "2025-02-10T16:50:16Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
