-
Notifications
You must be signed in to change notification settings - Fork 572
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
Gitea App bug #1969
Comments
looks to be a mariaDB issue. do you have that installed and set up? |
Its umbrel-store package, it must works after install from store, not? if i wanted setup separate components - i installed itself via docker-compose. |
i used the version from the store before and it worked like a charm. if that still doesn't work, access the debug terminal and folow this guide here ONLY DO THIS IF YOU NEED THOUGH!! |
I dont see where i can select type of db in appstore gitea page, its only Install button. |
i'll try installing it on my umbrel server (i just made a new one) and see if i can replicate the bug. all you did was install the one from the app store in umbrel right? no 3rd party stores? |
another question i have is when i upadate my version from 1.2.2 to 1.3 the server stops working? is there a way to prevent that? |
Yes, from official umbrel appstore. Newest release of umbrel, i upgrade it to 1.3 after install, all ok, reboot, then install some apps. Trouble only with portainer(after install all works but after some time - it cant connect to host. I install Dockage and it work like a charm.) and gitea. Works or not gitea on 1.2.2 - i dont know, i try in 1.3 |
alright. tonight, ill try to install umbrel 1.3 again, and then ill test gitea on it. |
i cannot seem to replicate this bug. |
upon further investigation, it may just be a firewall issue. i don't remember if umbrel comes with ufw, but make sure the ports are open. |
Hello,
latest umbrelOS 1.3
latest gitea 1.23.1 from store, first install
via browser http://umbrel.local:8085/ error ERR_CONNECTION_RESET
in docker logs
The text was updated successfully, but these errors were encountered: