{ [Error: ESOCKETTIMEDOUT] stack: [Getter] } Error When Accessing Setup Pages about plexrequests-meteor HOT 6 CLOSED

Are you running Meteor with any special parameters? Or are you running in production mode with NodeJS?

Can you navigate to the pages manually http://localhost:3000/couchpotato ? Does the Plex authentication page work http://localhost:3000/plex ?

from plexrequests-meteor.

I can navigate to couchpotato/plex/sonarr by going there without using the link on the admin page (or by clicking the link and then refreshing the page).

The socket timeout error was due to couchpotato not being set up correctly in the setting page I believe. I now get no error in my terminal when going to those status pages.

from plexrequests-meteor.

Yes your server console will output errors if something isn't working, that's expected. However, the web page should load regardless as it is suppose to indicate whether there is an error or not: so is this not happening? Or it is, but you've to refresh the page?

(Unrelated, I have noticed my admin interface sometimes requires a refresh to show, not sure if this is an iron:router issue, houston package issue, Meteor issue, or my app.

from plexrequests-meteor.

Once I fixed the connection issue with CP or Plex, I no longer get errors in the console. But the issue with the webpage not loading when using the link in the admin page is still there.

Sounds like you have the same issue with the admin page as I have with the status pages.

from plexrequests-meteor.

Something is applying the below style to the body element when clicking on links from the admin interface. Refreshing removes it, opening in a new tab removes it, or directly visiting the URL. So not sure what's adding it.

style="visibility: hidden;"

from plexrequests-meteor.

Temporarily fixed by making links open in a new tab, until I can more thoroughly look into it, seems to be an iron:router bug but not sure.

3ab2bbd

from plexrequests-meteor.