Initial draft

This commit is contained in:
qtchaos
2023-12-31 16:39:55 +02:00
parent baf2169306
commit 86cd905dc8
40 changed files with 2461 additions and 2909 deletions

View File

@@ -1,10 +1,10 @@
---
title: 'Troubleshooting'
---
# Troubleshooting
There is a possibility for something to go wrong while trying to deploy your own instance of movie-web. This page will contain common issues people come across while self-hosting and their solutions.
There is always a possibility for something to go wrong while trying to deploy your own instance of movie-web. This page will contain common issues people come across while self-hosting and their solutions.
## "Failed to find media, try again!" while searching
@@ -14,7 +14,6 @@ If it succeeds, the TMDB api key is correct and it will be a different issue.
If it does not work. Recheck your TMDB api key. **Make sure its the READ api key, not the normal api key.**
## Everything I try to watch fails
This is likely a misconfigured worker. Verify that the workers are the issue by going to `/admin` or `/#/admin`. Then clicking `Test workers`.
@@ -23,7 +22,6 @@ You should have at least 1 worker registered.
If any worker fails the test, you should double check its URL and double check if the worker has the correct code.
## I can't make an account or login
This is likely misconfigured or broken backend. Verify the backend by going to `/admin` or `/#/admin`. Then clicking `Test backend`.
@@ -36,7 +34,14 @@ If the version is not the latest version, you should update your backend instanc
If the name and description of the results don't match your own instance, make sure you have your backend URL set correctly.
## I updated from version 3 to version 4 but still see the old version
This is likely that you haven't installed the PWA version of movie-web. Please read the [upgrade guide](../3.client/5.upgrade.md)
It is likely that you haven't installed the PWA version of movie-web. Please read the [upgrade guide](../3.client/5.upgrade.md) for more details on the matter.
## I'm getting SSL issues when using a hosted postgres database
You are most likely missing the `postgres.ssl` variable on your backend, enable it and the connection should work.
## Permission denied to set parameter "session_replication_role"
Set the `MIKRO_ORM_MIGRATIONS_DISABLE_FOREIGN_KEYS` option to `false` in either your `.env` or your Docker command.