GooPlex to Gooby migration about gooby HOT 20 CLOSED

Yes, after a reboot they were not starting, however the system clean seems to have fixed it, thank you.

from gooby.

Awww, well first of all, the legacy GooPlex is still available: https://github.com/TechPerplexed/Gooby/tree/legacy
But honestly most of us who switched to the new Docker based Gooby never looked back, so I would definitely recommend you upgrade 😄

You can restore your Plex backup to /var/lib etc and Gooby should offer an import of your database. One thing you will have to change though is the location of your media, which will now sit in /Media (from within Plex). It's the small price to pay for progress I'm afraid 😆

You might want to consider Debian 9 instead of Ubuntu, I find the new 18.04 slightly more moody than Debian... but the choice is yours. Good luck with your upgrade!

from gooby.

Perfect, I'm glad you implemented that feature. I'll also move to Debian. Thank you!

from gooby.

Let me know if you have any questions :)

from gooby.

I started the upgrade process today on a brand-new Debian 9.8 install and it has not been without incident.

Everything seems to have installed fine, I manually moved the plex library files where they were supposed to be and chmod -R 777 the whole thing to ensure Gooby would be able to grab what it needs, it detected the files and asked if i wanted to import them and gave no errors through the process.

It never did ask me to claim the server, after it asked me to import the configuration it basically just finished and went back to the main menu. Initially I was able to go to mydomain.com:8443 and it had the plex interface but also said I had no servers running. I also created a backup that's about 12GB so it looks like it imported what it needed to. I've since restarted the server and now can't even get to mydomain.com:8443 I get a "ERR_CONNECTION_REFUSED" and plex.mydomain.com:8443 gives me a "DNS_PROBE_FINISHED_NXDOMAIN".

I also installed Watchtower and Portainer but am unclear how to access them (tried ports 9000 and 1024 but they didn't connect to anything).

from gooby.

So I went to remove Plex via the Gooby interface and it said it wasn't installed so I hit install and it seemed to start the container although once started, the previous issues remained as before. I've since done a proper remove and user configuration wipe via Gooby and have reinstalled without importing anything and will attempt to then manually migrate just my databases. It's still only accessible via mydomain.com:8443. Using the plex. domain prefix doesn't resolve to anything and I haven't been able to access Ombi/Portainer/Watchtower still.

from gooby.

First of all Plex: you weren't asked to claim your Plex server because you already have one (imported). that also means you won't need to go to plex.yourdomain:8443, just plex.yourdomain is enough.

Make sure you add A records with your provider for EACH of your services, so plex.yourdomain pointing to yourip, ombi.yourdomain pointing to yourip, etc. Watchtower is not a service you can access directly, it only checks for new containers.

You should never need to access anything using a port number, that is soooo GooPlex 1.0 🤣 Just service.yourdomain is sufficient now :)

Let me know if those pointers helped you any further!

Edit: to get the feel of Gooby, I suggest you create a temp server first without importing anything just yet or tinkering with chmod and/or ports - that way you will get the feel of it... I think that would probably an easier approach for you :)

from gooby.

Ah, that make sense, I'll make that change to my A records.

The database migration looks successful however, it appears whenever I restart the server the various services don't automatically start. I can start all of them by "Installing" Plex though via the Gooby interface. Any ideas on what's going on here?

from gooby.

What do you mean by they don't automatically start? After a reboot you mean? Try to run a system clean once, that will probably sort it (option E- C)

from gooby.

Spoke too soon, (Firefox tricked me when it auto-started and had the cached version up). So still not auto-starting after a reboot and I've been triggering the start by "installing" Plex (when I do so t does start all of the containers though)

from gooby.

Ok, how did you create your user? Did you have Gooby create it or did you do it manually? If so, the permissions may need to be corrected. Try this trick: type sudo -s to go to the root user. Then start gooby - it will tell you that you need to create a user. Then type your user (which already exists, but that doesn't matter). That should sort it... fingers crossed!

from gooby.

That worked! during the initial setup it did not ask me to create a user (but also didn't run it as root, just sudo privileges).

from gooby.

Yay! 🥂 Let's hope the rest is smooth sailing as well (as it should be) 👍

from gooby.

I've installed Plex, Organizr, Ombi, Netdata and Portainer (along with Watchtower).

I've set up the A records for each of these subdomains (I just put the server IP address in the A record, I didn't specify the port). I've also forwarded the corresponding ports specified in the docker-files. However, netdata seems to be the only one I can access. I think one potential problem is my actual server name is 'Plex' and it looks like because of this both organizr and plex are trying to use plex.mydomain.com? as I think that's what the variable ${ORGMENU} would resolve to? (but that doesn't explain why Ombi and Portainer aren't accessible).

I can access Plex via plex.tv or mydomain.com:8443 still. I'm not able to access any of the other applications this way though, nor by the ip address and port.

I appreciate the support, please don't let me ruin your weekend or anything, this isn't urgent.

from gooby.

What do you mean you have forwarded the ports? Honestly you can forget about ports altogether, they are no longer relevant in your setup other than some internal thingie that Gooby uses... What exactly did you setup?

from gooby.

On my router I forwarded ports 80, 8443, 9000 etc. I imagine I would at least need 80 and 8443 so Plex and Organizr are accessible outside of my home network (happy to be wrong though). How would an external user access Ombi or Organizr otherwise?

Regardless, would these port-forwards break anything? Typing in ombi.mydomain.com on a machine internal to my network takes me to my router configuration, and typing it in when outside of my network I get an 'error connection refused'

from gooby.

Oh I'm dreadfully sorry, I never realized you were running the server in your home - I had VPS on the brain :) Makes sense, I understand now what you meant by opening ports. Apologies for misunderstanding :)

So, just that we're on the same page altogether: you can access Plex by using the app.plex.tv address, but not the domain. Netdata works with your domain, but Ombi and Organizr do not?

Is there anything you did different with Netdata in your settings? Also, the fact you named your server "Plex" should not have anything to do with this, but I'll keep an open mind for sure :)

from gooby.

I should have specified I was doing it on a local server, not a VPS, sorry. Trying again today (although no changes since yesterday) and netdata is doing the same thing as the other services. So not sure what was going on yesterday. Plex is fully accessible through the app.plex.tv or mydomain.com:8443 but not plex.mydomain.com (and I do have 8443 fwd on my router to the server)

from gooby.

Try to open port 32400 for Plex... that might help.

As for the sites not being accessible - this is a longshot, but can you access your domains from OUTSIDE your house (mobile phone on data, library, etc?) but not from within your own home network?

from gooby.

It's been a week... I'm assuming your issue got sorted so I'll close this now. Feel free to reopen if you still have questions :)

from gooby.