search

kaangiray26 / forte

Self-hosted, music streaming platform
https://forte.buzl.uk/
GNU General Public License v3.0
342 stars 12 forks source link

Unable able to log in via default creds #109

Closed Dvalin21 closed 1 year ago

Dvalin21 commented 1 year ago

I'm getting forte and the db installed on Synology Nas via docker-compose via portainer. I get the following logs

Forte App logs ..: Starting forte :.. ..: Open the web player at https://forte.buzl.uk/ :.. ..: Server: http://0.0.0.0:3000/ :..

Database logs PostgreSQL Database directory appears to contain a database; Skipping initialization 2023-04-21 07:04:12.744 UTC [1] LOG: starting PostgreSQL 15.2 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit 2023-04-21 07:04:12.744 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2023-04-21 07:04:12.744 UTC [1] LOG: listening on IPv6 address "::", port 5432 2023-04-21 07:04:13.052 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2023-04-21 07:04:13.810 UTC [31] LOG: database system was shut down at 2023-04-21 07:03:43 UTC 2023-04-21 07:04:13.841 UTC [38] FATAL: the database system is starting up 2023-04-21 07:04:13.899 UTC [1] LOG: database system is ready to accept connections 2023-04-21 07:09:13.909 UTC [29] LOG: checkpoint starting: time 2023-04-21 07:09:15.777 UTC [29] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.658 s, total=1.868 s; sync files=2, longest=0.424 s, average=0.329 s; distance=0 kB, estimate=0 kB

I would think that Forte is not connecting to the database, but not sure why. Thanks in advance.

kaangiray26 commented 1 year ago

Usually once you run the forte server via docker it hosts the admin dashboard at 0.0.0.0:3000. And if you want to connect to your own server, let it be locally or publicly, you go to the https://forte.buzl.uk web player and enter your server address there.

Did you try the default credentials on 0.0.0.0:3000 ?

edit: I think there is a bug in the dashboard login page, you can login with the default credentials if you press the enter key instead of the Log in button.

kaangiray26 commented 1 year ago

Please try out the new version, Forte 4.1

Dvalin21 commented 1 year ago

Please try out the new version, Forte 4.1

Thanks Ill let you know the results

Dvalin21 commented 1 year ago

@kaangiray26 Hello, sorry for the late report, but I'm still having the same issue. I am getting the following errors from the database and forte

..: Server: http://0.0.0.0:3000/ :.. ..: Starting forte :.. ..: Open the web player at https://forte.buzl.uk/ :.. ..: Server: http://0.0.0.0:3000/ :.. ..: Starting forte :.. ..: Open the web player at https://forte.buzl.uk/ :.. ..: Server: http://0.0.0.0:3000/ :.. ..: Starting forte :.. ..: Open the web player at https://forte.buzl.uk/ :.. ..: Server: http://0.0.0.0:3000/ :.. ..: Starting forte :.. ..: Open the web player at https://forte.buzl.uk/ :.. ..: Server: http://0.0.0.0:3000/ :.. ..: Starting forte :.. ..: Open the web player at https://forte.buzl.uk/ :.. ..: Server: http://0.0.0.0:3000/ :..

PostgreSQL Database directory appears to contain a database; Skipping initialization 2023-04-28 02:25:17.268 UTC [1] LOG: starting PostgreSQL 15.2 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit 2023-04-28 02:25:17.268 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2023-04-28 02:25:17.268 UTC [1] LOG: listening on IPv6 address "::", port 5432 2023-04-28 02:25:17.330 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2023-04-28 02:25:17.384 UTC [30] LOG: database system shutdown was interrupted; last known up at 2023-04-28 02:22:03 UTC 2023-04-28 02:25:17.641 UTC [30] LOG: database system was not properly shut down; automatic recovery in progress 2023-04-28 02:25:17.925 UTC [30] LOG: redo starts at 0/1501590 2023-04-28 02:25:18.138 UTC [30] LOG: invalid record length at 0/1936B38: wanted 24, got 0 2023-04-28 02:25:18.139 UTC [30] LOG: redo done at 0/1935BA8 system usage: CPU: user: 0.01 s, system: 0.01 s, elapsed: 0.21 s 2023-04-28 02:25:18.266 UTC [28] LOG: checkpoint starting: end-of-recovery immediate wait 2023-04-28 02:25:18.267 UTC [37] FATAL: the database system is not yet accepting connections 2023-04-28 02:25:18.267 UTC [37] DETAIL: Consistent recovery state has not been yet reached. 2023-04-28 02:25:19.997 UTC [44] FATAL: the database system is not yet accepting connections 2023-04-28 02:25:19.997 UTC [44] DETAIL: Consistent recovery state has not been yet reached. 2023-04-28 02:25:20.991 UTC [28] LOG: checkpoint complete: wrote 924 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.021 s, sync=2.221 s, total=2.783 s; sync files=250, longest=0.917 s, average=0.009 s; distance=4309 kB, estimate=4309 kB 2023-04-28 02:25:21.399 UTC [1] LOG: database system is ready to accept connections