Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QBITTORRENT] Default config results in broken app. #581

Closed
indivisionjoe opened this issue Jun 22, 2021 · 4 comments
Closed

[QBITTORRENT] Default config results in broken app. #581

indivisionjoe opened this issue Jun 22, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@indivisionjoe
Copy link

Describe the bug
If you use all of the default settings for qbittorrent, the app installs. However, in the GUI it is stuck in the "deploying" state with no logs available.

To Reproduce
Install qbittorrent. Give it a name. But, otherwise leave all default settings as-is.

Expected behavior
I expected the app to finish deploying and then become available on port 36039. But, it never becomes "active" or available on the port.

Additional context
I was able to get the app to work by changing the network type from NodePort to ClusterIP and selecting the "Enable Host Networking" option. However, this puts the app at port 8080 and, I've been told, this networking config is not ideal.

@indivisionjoe indivisionjoe added the bug Something isn't working label Jun 22, 2021
@indivisionjoe
Copy link
Author

Update. After uninstall and reinstalling a few times with different settings I was able to get a 100% default install to turn active. I'm not sure how/why. Perhaps the first time installing takes longer than expected?

@stavros-k
Copy link
Member

Installing an app that uses PVC some times takes a few minutes (2-3max usually) to create the PVC storage.
If it takes longer and never deploys, please let us know by opening an issue again, or on our Discord

@Ornias1993
Copy link
Member

In case there is an issue (which can also not be excluded fully):
Please actually add logs to your issue, because without there is really not much we can do for you :(

@truecharts-admin
Copy link
Collaborator

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists

@truecharts truecharts locked and limited conversation to collaborators Feb 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants