[Support] Linuxserver.io - Quassel-Web

[linuxserver.io]

Application Name: Quassel-Web

Application Site: https://github.com/magne4000/quassel-webserver

Docker Hub: https://hub.docker.com/r/linuxserver/quassel-web/

Github: https://github.com/linuxserver/docker-quassel-web

 

Please post any questions/issues relating to this docker you have in this thread.

 

If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

[ICDeadPpl]

Just curious, when is this going to be merged in template repo? It's been over a week since the announcement.

[CHBMB]

On 5/7/2019 at 9:17 AM, ICDeadPpl said:

Just curious, when is this going to be merged in template repo? It's been over a week since the announcement.

This has been merged now.  Should be in CA within an hour or so.

[artafinde]

I'm experiencing an issue with quassel-web. The login screen works and when I input username/password and click on login the screen shows "Connecting" and stuck there for ever.

Docker logs show:

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] QUASSEL_CORE set, injecting env variables into settings.js
[cont-init.d] setting file permissions this may take some time ...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
SETTINGS: Using /app/quassel-web/settings-env.js
quassel-webserver listening for http connections on port 64080
GET / 304 942.431 ms - -
GET /stylesheets/fonts.css 304 2.378 ms - -
GET /javascripts/jquery.min.js 304 0.636 ms - -
GET /stylesheets/mobile.css 304 2.549 ms - -
GET /javascripts/angular.min.js 304 17.267 ms - -
GET /javascripts/angular-aria.min.js 304 17.413 ms - -
GET /javascripts/ui-bootstrap-tpls.min.js 304 17.470 ms - -
GET /javascripts/bootstrap-tokenfield.min.js 304 1.383 ms - -
GET /javascripts/scrollglue.js 304 1.728 ms - -
GET /javascripts/favico-0.3.10.min.js 304 1.981 ms - -
GET /javascripts/ng-quassel.js 304 0.538 ms - -
GET /javascripts/angular-sanitize.js 304 3.276 ms - -
GET /javascripts/angular-dnd.min.js 304 3.382 ms - -
GET /javascripts/angular-notify.min.js 304 3.534 ms - -
GET /javascripts/libquassel.js 304 3.728 ms - -
GET /javascripts/angular-init.js 304 3.618 ms - -
GET /javascripts/angular-directive.js 304 17.089 ms - -
GET /javascripts/angular-filter.js 304 17.092 ms - -
GET /javascripts/angular-controller.js 304 0.863 ms - -
GET /stylesheets/theme-default.css 200 994.758 ms - 98261
GET /images/quassel-logo.png 200 14.240 ms - 511
GET /settings 304 1.165 ms - -

 

I'm using Firefox and the Quassel-code is _not_ running in unraid (it's an a VPS)

[MulletBoy]

I am having a similar issue to the person above me, I have the quassel-core docker running and can access it fine from the desktop client, but when using the quessel-web docker i input the login credentials and it just spins at "connecting" forever.

 

In the quassel-core logs I can see the following

 

2024-03-30 18:47:14 [Info ] Client connected from 172.18.0.1

 

If I connect from my desktop client the logs show

 

2024-03-30 18:47:58 [Info ] Client connected from 192.168.1.10
2024-03-30 18:47:58 [Info ] Client 192.168.1.10 initialized and authenticated successfully as "username" (UserId: 1).

 

im using identical credentials for both, but the web client never triggers the second authentication line in the logs (sucess or fail...) its like it just isnt pushing the full request through?

 

any support on this would be appreciated, i suspect this is a pretty rarely used docker given how quiet this thread is...