question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Support] Various issues on linux

See original GitHub issue

Hey, just tried to run EmbyStat, and failed in various ways. Here is a list of problems I encountered:

  • No documentation on volumes to mount

  • “Did you try to run a dotnet command?” message when attempting to mount /app I ended up mounting /app/Logs and /app/Settings, I found them in some other issues comments. I don’t know if there is something else to mount. That’s just what I’ve got currently.

  • nightly-linux docker image is a windows image Well this one is a wtf one 😃

  • Failed first sync in the Wizard: POST https://<my-embystat-url>/api/emby/server/token 400 (Bad Request) This was using the beta-linux image. Shouldn’t this request be sent to the actual emby instance instead of the embystat one? They’re both on the same server, and the embystat domain is stats.theembydomain

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:33 (15 by maintainers)

github_iconTop GitHub Comments

1reaction
leon1995commented, Aug 27, 2019

sorry that was a bit unclear. I do mean a user authentication to embystat itself. im glad to hear that its already on the list! 😃

1reaction
mregnicommented, May 25, 2019

LOL, thanks for the checklist!!

At the moment I can’t rebuild the containers since I’m switching between build servers. But thanks for mentioning it!

As for the documentation, I know there is almost none at the moment. Since I don’t have a stable beta release yet it changes a lot still. After the nosql update I will move the database to a folder that can be mounted. I still have no idea why we get the “did you try to run a dotnet command” error if you just mount the whole /app folder.

For the failed sync, I have to look into that. It indeed should go to the emby server and not to the embystat ofcourse.

I’ll keep you posted on the bugs you logged, thanks for your time testing the app and reporting the bugs!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting Linux: Problems That Drive You Mad and ...
When it comes to troubleshooting Linux problems related to performance, the tricky part is nailing down the root cause of those troublesome ...
Read more >
Troubleshooting hardware problems in Linux
Keep in mind that hardware issues in Linux may come from many different sources, including devices, modules, drivers, BIOS, networking, and even ...
Read more >
3 Common Linux Troubleshooting Techniques for ...
These are fundamental troubleshooting tools that will help you find issues on a network.
Read more >
A Field Guide to Linux Support Problems
Here at Sirius we hear a lot from our customers and prospective customers about the kinds of problems they have with Linux and...
Read more >
Troubleshooting tips for the 5 most common Linux issues
Learn how to tackle the most common challenges Linux desktop users encounter.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found