Closed adocampo closed 4 years ago
Are you running Docker on your server? There's a PR to add Docker support that was opened recently: https://github.com/sungshon/PimpMyStremio/pull/85
This might make things a bit simpler for you. I'm not sure yet, but the Docker image might break the auto-updater though.. (checked the Docker PR in the meanwhile, it shouldn't break the auto-updater)
The chosen app data dir on your server does seem strange, this directory is chosen based on the APPDATA
process environment variable, which might be different on your server compared to your PC. (see: https://github.com/sungshon/PimpMyStremio/blob/master/src/lib/dirs/rootDir.js#L4 )
Based on your logs, I can tell that it expects this folder to exist: /root/.local/share/
, and this is probably the APPDATA
folder on that server. If it does not exist, could you create it and give write access to the folder for the user that runs PMS? Otherwise, you could try changing the APPDATA
environment variable to something else before running the app..
After you fix the APPDATA
issue, you should try deleting all user configs and PMS, then downloading + starting it again. (so it can update again and hopefully use the correct folder)
Actually, considering this logic:
let rootDir = process.env.APPDATA || (process.platform == 'darwin' ? process.env.HOME + '/Library/Preferences' : process.env.HOME + '/.local/share')
It looks like process.env.APPDATA
does not exist on your server, so it falls back to process.env.HOME + '/.local/share'
, so the HOME
process environment variable in your case is /root/
, leading to /root/.local/share
, which probably does not exist. And this most probably caused all the issues you're having.
Ok, I did some more tests, and they were... well, a bit weird.
No, I wasn't using docker, and as you suggested, all the fuss came for the APPDATA environment variable, which was in blank. I just created the /root/.local/share
directory and started PMS again, it upgraded, restarted and it worked as expected. :tada:
PS: I tried also @sleeyax's docker image, but it ended with an error when adding the add-on on stremio Yet I see the json on that URI
The fun fact is setting up stremio locally on the headless server failed with the same error at first, but then started to work after a while with no action by my side, just waited a couple of minutes.
I'm opening a new issue for the pms-docker and in the meanwhile I will use pms manually installed, but this is not ideal, as I have all my services dockerized.
I tried also @sleeyax's docker image, but it ended with an error when adding the add-on on stremio
Looking at your print screen for the manifest URL, it looks like it's not using SSL. Stremio only loads addons from SSL enabled links, the only exception is local links (127.0.0.1
and localhost
), that's why the LAN feature is so important, as it enables SSL.
After testing successfully PMS on my PC, I want to let it running on my home server, which is 24/7 online, so I can access PMS on all my stremio devices like firestick or android seamlessly.
I copied the x86 binary to the server and ran it, with this output
As I saw it was listening on 127.0.0.1:7777, I opened the file
./LocalData/assets/LocalData/PimpMyStremio-userConfig.json
and let it like this:Now, output shows this:
And I can see now is listening on all the interfaces
But when I try to access from my computer through https://192.168.1.100:7777 or the hostname generated, in my case
https://192-168-1-100.519b6502d940.stremio.rocks:7777
, I get the errorCannot GET /
As my server is headless, I configured back to "No (local)" and tried CLI internet browser "links", and the same error appears
It's strange, as I tested it on my computer without problems in "LAN" mode
Both computers have static IP, but I noticed Stremio files are placed in different places on my computer (
~/.local/share/PimpMyStremio
) and my server (on a directory called LocalData on the same place where PimpMyStremio binary is placed). Directory structure is also different.Am I missing something?