Cant open any services

[Axekinn]

So as I said here : #76

I took a screenshot of what was working, but everything else isn't working.

I understand that a screenshot showing that it isn't working isn't very helpful, but it's all I have.

Otherwise, here are the logs from my containers:

Sonarr : https://privatebin.net/?f0c0ab1c324fdca2#AUpk1oEcFU1uaXEnXVr46y6BeJACEB4qH7ciPwExVjr3
Homarr : https://privatebin.net/?93b91c1f0740aa6b#AuWCd4mwYr2pJDLpjFsxhLAAFP6yCvEQ5YjYoJ1wedTW
Flaresolverr : https://privatebin.net/?497c321a6ef0f36f#FpSug72T5tF9Cho9tEubyqBALNtf3JQP8Wic8zvuhfuq
Plex : https://privatebin.net/?9e6c114bae2e3a38#7jnV4mRLRAgd175YcM458huJRNtoUyukKz89iYquPh1X
Overseerr : https://privatebin.net/?36dfc3cb88bc75ad#HKXDUiugvyJ8NcuUmuDZsmBwb4if3HJLWmNrrCqc2rzi
Radarr : https://privatebin.net/?8edbcb4320f6c68f#8SEDKMn7SZbagwd7jq6K66yrPQojuoCGSgdcu7Udnehw
Bazarr : https://privatebin.net/?36a7ab68b97541c2#A96H2LsARjbpNEUQXGmnbVb89sARg9zgZAJYxXbbZ5cR
Lidarr : https://privatebin.net/?3d9dceb149001a87#8bCfJoCYFqcFyRzX4mfjp93NvzSMbs25wmc4StgnvmHs
Prowlarr : https://privatebin.net/?fc0da6eb2ba6c9b8#Ha2nFY5G61sYAefSUDZ9mjkYFCLfE5uyKA9ZPtd8JkYF

[Axekinn]

Well, I think I'll have to figure it out myself, and the problem seems to be a simple permission issue because initially the setup is done via a NAS, meaning that all the configuration files are stored on the NAS (including torrents) while the GitHub repo is on another PC on the network, so sudo docker compose up -d is done on my PC and not the NAS, and it wasn't working there. So I reinstalled it on my local drives, and it works except for flaresolverr.

We should see if it's possible to fix this problem during installation, because right now I don't know what to do to give permissions (if that's what it is) on my NAS, and whether it's done generically during installation for everyone, if the configuration folder is done via a network drive.

Also, for beginners, because if I understand correctly, this repo is designed for beginners, it would be great to have a list of where to go, because I had to search for it myself manually in Docker Compose.

Here's how it could be presented:

sonarr : http://localhost:8989/
radarr : http://localhost:7878
lidarr : http://localhost:8686
bazarr : http://localhost:6767
prowlarr : http://localhost:9696
jackett : http://localhost:9117
flaresolverr : http://localhost:8191
qbittorrent : http://localhost:8080

PS: QbittorrentUI is installed via a password, but the default password does not work, so it is impossible to access the interface without knowing the password (and I dont known the password), and it cannot be changed via the configuration file.

[Luctia]

I'm sorry you're having difficulty with these services. However, the purpose of this repository/tool is not to provide a central point of knowledge for all of these services. As a matter of fact, I probably haven't used half of these services myself. This is why we link to the documentation of all of these services in the README.

Instead, it's a tool that helps users who are new to Docker and/or Linux to deploy these services using Docker, and makes their lives slightly easier by attempting to set the correct file permissions on the host.

If you're having trouble with these services individually, I suggest looking at the docs for the service in question. For example, for your qBittorrent problem, it says in the docs that "a temporary password for the admin user will be printed to the container log on startup." I don't have the time or knowledge to help with problems or questions that are specific to services that I haven't developed/helped to develop.

This is the right place to indicate problems with, for example, Docker images that are broken (for example, when support for a service is dropped) or if the permissions aren't being set correctly on the host.

As for your remark about permissions: the repository is very small, so I never intended for it to set permissions on a machine other than the one it is installed on, nor do I think it's necessary. Again, the repo is small and can easily be removed after inital setup if desired, and providing support for changing permissions on another machine would require quite a bit of extra work (especially if it is to be fail-safe and easily understandable for new users). If this is a feature you desire strongly, you can add it to the issues as a suggestion and someone might pick it up at some point.

As for your remark on ports, I think this is a valid ask and I'll add it some time soon. Where do you think would be a good place? I'm thinking of either in the README or during setup, when the docker-compose file has been created. I'd love your input.

[Axekinn]

In the FAQ.
You can write : where to go after started my container ?
A: all links mentionned above.