server name: error fetching (failed to parse

[grilor]

windows 11 pro
unzipped the files into a folder
ran the dynamiXMain.exe
filled in all the information required
once clicking the save button i get this error
Server Name: error fetching (failed to parse: http://xxx.xxx.xxx.xxx:32400)

I have tried local ip 192.168.xxx.xxx
i have tried external ip xxx.xxx.xxx.xxx (x are to hide my ip)

i deleted the config file and did the setup 3 more time all with the same issue

EDIT:
fixed the 1st part. i had some how put a space between the last ip number and the :

but now im getting this error and this is over my head now:

An error occurred: ('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))

i have looked into this and now im stuck

[TheImaginear]

Are you sure you entered the plex token correctly? That seems to be showing that the plex server is rejecting the connection. Make sure you have entered the plex token correctly (https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/), be sure that your server is available in your browser at the url you entered, and try this in your command prompt to ensure that you are able to establish a connection with the token and url: curl -X GET http://<server_ip>:32400/?X-Plex-Token=<your_token>

I would recommend removing the config file before updating your token to ensure its updated correctly.

[grilor]

I have a vhost and Incan login to my server with the url:port without any issues. I can even sign in with my internal IP:port just fine. But your app just can't seem to get past what ever is going on. No clue what to try next

…

On Tue, Dec 17, 2024, 10:05 p.m. TheImaginear ***@***.***> wrote: Are you sure you entered the plex token correctly? That seems to be showing that the plex server is rejecting the connection. Make sure you have entered the plex token correctly ( https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/), be sure that your server is available in your browser at the url you entered, and try this in your command prompt to ensure that you are able to establish a connection with the token and url: curl -X GET http:// <server_ip>:32400/?X-Plex-Token=<your_token> I would recommend removing the config file before updating your token to ensure its updated correctly. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AECM22IB4XGSBXUW5BQBH532GDJ55AVCNFSM6AAAAABTZUFJT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJQGEZDSOBRHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TheImaginear]

I'm certain it has something with how it interacts with the vhost. Ill try to address this in a future build.

[grilor]

Sounds good, thanks!

…

On Thu, Dec 19, 2024, 12:43 a.m. TheImaginear ***@***.***> wrote: I'm certain it has something with how it interacts with the vhost. Ill try to address this in a future build. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AECM22KDA4DNC74SM3O6UZ32GJFIFAVCNFSM6AAAAABTZUFJT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSG43DQMBXGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TheImaginear]

In plex settings. Network, Secure Connections. Set to Preferred. I receive your exact error when that is set to "Required"

[grilor]

Ok, I'll check it out.

…

On Mon, Dec 30, 2024, 4:19 p.m. TheImaginear ***@***.***> wrote: In plex settings. Network, Secure Connections. Set to Preferred. I receive your exact error when that is set to "Required" — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AECM22JRWDBAGJ6DFKLGF532IGTEPAVCNFSM6AAAAABTZUFJT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVHA4DCOBQG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TheImaginear]

Were you able to get it working? Ill be closing this issue on 1/10 if there is no response.

[grilor]

No, not yet. But it's been a rough xmas and new year here. Had a death in the family and daughter might need knee surgery. but close it and if I need to I can repost a new one if needed. Sorry for taking up your time.

…

On Mon, Jan 6, 2025, 3:10 p.m. TheImaginear ***@***.***> wrote: Were you able to get it working? Ill be closing this issue on 1/10 if there is no response. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AECM22K3NKXT7T7INYRSIWD2JLIKDAVCNFSM6AAAAABTZUFJT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTG42DCOBTGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TheImaginear]

No problem at all, just wanted to clean up the issues that I could! I'll restrict this issue to the two of us for now. Hope things are better for you soon, happy new year.