After update room broken

[rinjuu123]

Hello,

me again. After i updated the docker with the command you provided me, the room i created is now broken.
I can't add new videos and under the settings of the room i have to "Claim Room" again.
When i change to the settings, i get a error message in the lower right corner that tells me "failed to load room settings".
And it's true, the room has no set settings anymore, but i can't set them again.

It would be no problem, when i could create a new room, but that fails too. temporary and permanent rooms.
"An unknown error occurred. Try again later." is the error message.

Here are the logs:

Opentogethertube

yarn workspace v1.22.19
yarn run v1.22.19
$ /usr/app/node_modules/.bin/sequelize-cli db:migrate

Sequelize CLI [Node: 18.16.0, CLI: 6.6.1, ORM: 6.32.0]

Loaded configuration file "config/config.mjs".
Using environment "production".
No migrations were executed, database schema was already up to date.
Done in 0.98s.
Done in 1.52s.

opentogethertube@0.3.0 start
yarn workspace ott-server start

yarn workspace v1.22.19
yarn run v1.22.19
$ node --experimental-specifier-resolution=node --loader ts-node/esm app.ts
(node:96) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:96) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time.
2024-03-05 11:22:14 config info Loading extra base config from /usr/app/env/docker.base.toml
2024-03-05 11:22:14 config warn No config found at /usr/app/env/base.toml
2024-03-05 11:22:14 config info Loading environment config from /usr/app/env/production.toml
2024-03-05 11:22:14 app info Environment: production
2024-03-05 11:22:14 app info Is Heroku? false
2024-03-05 11:22:14 app info Is Docker? true
2024-03-05 11:22:14 app info Database mode: postgres
2024-03-05 11:22:14 app info Search enabled: true
2024-03-05 11:22:14 app info Search provider: youtube
2024-03-05 11:22:14 app info Rate limiting enabled: true
2024-03-05 11:22:14 db info Database models loading
2024-03-05 11:22:14 db info Using database: opentogethertube
2024-03-05 11:22:14 redisclient info Building redis clients
2024-03-05 11:22:14 app info Latency to redis: 5.142517000436783ms
2024-03-05 11:22:14 balancer warn Load balancing is disabled
2024-03-05 11:22:14 roommanager info Starting room manager
2024-03-05 11:22:14 infoextract info Enabled video services: youtube, vimeo, dailymotion, direct, hls, tubi, reddit, googledrive, peertube, pluto
2024-03-05 11:22:14 infoextract warn Google Drive API key is not set, disabling Google Drive service
2024-03-05 11:22:14 app info Server started on  8080
2024-03-05 11:22:22 app info > GET /api/auth/grant
2024-03-05 11:22:22 app info > GET /api/user
2024-03-05 11:22:32 app info > GET /api/auth/grant
2024-03-05 11:22:32 app info > GET /api/user
2024-03-05 11:22:32 app info > GET /api/room/ods
2024-03-05 11:22:33 app info > GET /api/room/ods
2024-03-05 11:22:34 app info > GET /api/room/
2024-03-05 11:22:35 app info > GET /api/room/ods

opentogethertube_postgres

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /tmp ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /tmp -l logfile start

waiting for server to start....2023-10-20 21:57:06.760 UTC [48] LOG:  starting PostgreSQL 15.4 (Debian 15.4-2.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-10-20 21:57:06.762 UTC [48] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-10-20 21:57:06.768 UTC [51] LOG:  database system was shut down at 2023-10-20 21:57:06 UTC
2023-10-20 21:57:06.775 UTC [48] LOG:  database system is ready to accept connections
 done
server started
CREATE DATABASE


/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

waiting for server to shut down....2023-10-20 21:57:07.015 UTC [48] LOG:  received fast shutdown request
2023-10-20 21:57:07.017 UTC [48] LOG:  aborting any active transactions
2023-10-20 21:57:07.019 UTC [48] LOG:  background worker "logical replication launcher" (PID 54) exited with exit code 1
2023-10-20 21:57:07.020 UTC [49] LOG:  shutting down
2023-10-20 21:57:07.027 UTC [49] LOG:  checkpoint starting: shutdown immediate
2023-10-20 21:57:07.255 UTC [49] LOG:  checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.015 s, sync=0.211 s, total=0.235 s; sync files=301, longest=0.006 s, average=0.001 s; distance=4217 kB, estimate=4217 kB
2023-10-20 21:57:07.264 UTC [48] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

2023-10-20 21:57:07.343 UTC [1] LOG:  starting PostgreSQL 15.4 (Debian 15.4-2.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-10-20 21:57:07.344 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-10-20 21:57:07.344 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-10-20 21:57:07.353 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-10-20 21:57:07.358 UTC [64] LOG:  database system was shut down at 2023-10-20 21:57:07 UTC
2023-10-20 21:57:07.367 UTC [1] LOG:  database system is ready to accept connections
2023-10-20 22:02:07.431 UTC [62] LOG:  checkpoint starting: time
2023-10-20 22:02:20.435 UTC [62] LOG:  checkpoint complete: wrote 132 buffers (0.8%); 0 WAL file(s) added, 0 removed, 0 recycled; write=12.964 s, sync=0.028 s, total=13.005 s; sync files=97, longest=0.006 s, average=0.001 s; distance=731 kB, estimate=731 kB
2023-10-20 22:03:51.154 UTC [1] LOG:  received fast shutdown request
2023-10-20 22:03:51.156 UTC [1] LOG:  aborting any active transactions
2023-10-20 22:03:51.159 UTC [1] LOG:  background worker "logical replication launcher" (PID 67) exited with exit code 1
2023-10-20 22:03:51.160 UTC [62] LOG:  shutting down
2023-10-20 22:03:51.161 UTC [62] LOG:  checkpoint starting: shutdown immediate
2023-10-20 22:03:51.165 UTC [62] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.006 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=658 kB
2023-10-20 22:03:51.174 UTC [1] LOG:  database system is shut down
 
PostgreSQL Database directory appears to contain a database; Skipping initialization
 
2024-03-05 11:22:08.080 UTC [1] LOG:  starting PostgreSQL 15.4 (Debian 15.4-2.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2024-03-05 11:22:08.081 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-03-05 11:22:08.081 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-03-05 11:22:08.083 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-03-05 11:22:08.088 UTC [29] LOG:  database system was shut down at 2024-03-05 11:22:07 UTC
2024-03-05 11:22:08.094 UTC [1] LOG:  database system is ready to accept connections
2024-03-05 11:27:08.165 UTC [27] LOG:  checkpoint starting: time
2024-03-05 11:27:08.176 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.002 s, total=0.011 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB

opentogethertube_redis

1:C 05 Mar 2024 11:19:38.055 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 05 Mar 2024 11:19:38.055 * Redis version=7.2.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 05 Mar 2024 11:19:38.055 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 05 Mar 2024 11:19:38.056 * monotonic clock: POSIX clock_gettime
1:M 05 Mar 2024 11:19:38.057 * Running mode=standalone, port=6379.
1:M 05 Mar 2024 11:19:38.058 * Server initialized
1:M 05 Mar 2024 11:19:38.058 * Loading RDB produced by version 7.2.2
1:M 05 Mar 2024 11:19:38.058 * RDB age 1 seconds
1:M 05 Mar 2024 11:19:38.058 * RDB memory usage when created 0.99 Mb
1:M 05 Mar 2024 11:19:38.058 * Done loading RDB, keys loaded: 32, keys expired: 0.
1:M 05 Mar 2024 11:19:38.058 * DB loaded from disk: 0.000 seconds
1:M 05 Mar 2024 11:19:38.058 * Ready to accept connections tcp
1:signal-handler (1709637726) Received SIGTERM scheduling shutdown...
1:M 05 Mar 2024 11:22:06.611 * User requested shutdown...
1:M 05 Mar 2024 11:22:06.611 * Saving the final RDB snapshot before exiting.
1:M 05 Mar 2024 11:22:06.616 * DB saved on disk
1:M 05 Mar 2024 11:22:06.616 # Redis is now ready to exit, bye bye...
1:C 05 Mar 2024 11:22:07.404 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 05 Mar 2024 11:22:07.404 * Redis version=7.2.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 05 Mar 2024 11:22:07.404 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 05 Mar 2024 11:22:07.404 * monotonic clock: POSIX clock_gettime
1:M 05 Mar 2024 11:22:07.405 * Running mode=standalone, port=6379.
1:M 05 Mar 2024 11:22:07.405 * Server initialized
1:M 05 Mar 2024 11:22:07.405 * Loading RDB produced by version 7.2.2
1:M 05 Mar 2024 11:22:07.405 * RDB age 1 seconds
1:M 05 Mar 2024 11:22:07.405 * RDB memory usage when created 0.99 Mb
1:M 05 Mar 2024 11:22:07.406 * Done loading RDB, keys loaded: 32, keys expired: 0.
1:M 05 Mar 2024 11:22:07.406 * DB loaded from disk: 0.000 seconds
1:M 05 Mar 2024 11:22:07.406 * Ready to accept connections tcp

Could you please help me with that? Did i do something wrong?

[rinjuu123]

Ok, i found out that it has to do, that i created a subdomain and got over this onto my homepage. With the old link, i can do anything normaly. Do you know how i can change it? Or do i have to reinstall OTT?

[dyc3]

If you try to go directly to a permanent room in your browser (eg. https://xxx.xxx.de/room/ods ) Does it say "Connected" in the top left?

Also, I'm not sure your apache config is right. It doesn't look like it's proxying websockets.

[rinjuu123]

When i go directly to "https://xxx.xxx.de/room/ods " it says "Connecting...." in the Top Right corner.
I will look into the apache config. I try t learn anything. sorry

[dyc3]

Ah, yeah that's probably part of the problem. That indicates that the websocket connection isn't being established.

[rinjuu123]

Ok, i put this in the apache2 config

   RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
   RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC]
   RewriteRule .* ws://localhost:8080%{REQUEST_URI} [P]

and it works like a charm. Thank you!