Guacamole interface only shows a blank page #97
Comments
|
I'm seeing a similar problem. It seems to be the proxy (it worked without the proxy). I see some exta settings are needed here: https://guacamole.apache.org/doc/1.4.0/gug/reverse-proxy.html#proxying-with-nginx |
|
|
I'm having the same issue. My calibre instance lives behind a nginx-proxy-manager. I've pinned my docker-compose to the I've tried accessing the UI via |
|
If only the calibre version 5.x is working but version 6.x not, then keep in mind, that version 6 needs a newer kernel version than version 5. Many of Synology NAS e.g. are running with kernel 3.10 and users are reporting that calibre won't start with this old kernel. |
|
@theilenz I can't speak for @scottsuch's setup, but if you double check the Environment section in the issue description, this problem is taking place with a modern kernel version (Linux 5.10). |
|
I'm not running on Synology. I'm running on an Intel NUC. The host is an Ubuntu 20.04 installation running |
|
I have seen the kernel version in the environment section, but scottssuch's were missing at this time. However, if the guacamole shows only a blank page, especially without reverse proxy, but direct connection, than it might be possible, that calibre isn't running at all. Maybe just try and start it inside the container to see what it reports then. |
|
I exec'd into the container and ran the following I'm not certain if I did that right so feel free to point out if I'm missing something. |
|
This is happening to me right now, after this change. Calibre isn't starting up and the Guacamole Client is also displaying a blank screen. The furthest that I got was something about a child process lock, but I haven't been able to reproduce. Falling back to 6.4.0 makes everything work again. |
|
With the 6.5.0 release I'm now getting this... Logs are here: |
|
duplicate #102 |
|
That fixed the UI error but the screen is still black/blank. |
|
I'm also having issues with Calibre on Unraid. I'm getting the same, "Error launching startup command: Failed to clsoe file descriptor for child process (Operation not permitted)". text error warn system array login [2022-09-22 17:56:45] [Connection 1] Closing connection with error: Error: WS was inactive for too long |
|
dupe #102 |
I'm getting the same error. I was able to get Calibre working by rolling back to 6.4. This would seem to indicate a regression somewhere along the way. I start Calibre as needed with a shell script containing the following: (the ":amd64-v6.4.0-ls178" bit is new as of a few minutes ago)
I only have Calibre running while I'm actively managing my library; it's set to route the interface to port 89, which I then access from my desktop as http://server:89. No proxy server is involved. When I'm not working with the library and only need to be able to download ebooks from my library to a reader, I use COPS, which is set to run all the time. (If it matters, my server is a homebuilt Ryzen 5 2600 running Flatcar Container Linux.) |
|
@salfter this was mentioned 2x above with just the dupe comments, but the fix is to run your container with the following. |
The only occurrence of that string in the messages above (only in the OP, actually) suggested it didn't make a difference. There are several wall-of-text posts (inclusions of logfiles and such) that make finding any useful suggestions difficult. That said, I gave it a shot anyway...and it worked. w00t! |
|
I removed the |
|
can someone explain how to do the above modifications to the docker config? I have no idea. |
|
It's in the readme and the run/compose samples |
|
@yegods |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Can somebody tell me how to do this in Unraid? Adding it to the CLI Args doesn't work, creating a new variable wasn't successful for me as well (or I did it wrong as I'm a complete n00b at this...) |
|
@Buba81 i ran into the same problem on unraid today. |
Well, I never even seemed to notice the advanced tab ;-) |
|
Adding the CLI command to the container on Unraid did not fix the problem for me. |
|
@wallywhatever just to make sure, it looks like this?
|
|
Yup that did it. Too many similar fields on these docker pages for me to figure it out. Thanks! |
|
Hi all, I'm still having the original problem of a blank white screen. I was able to get rid of the pop-up error with the --security-opt="seccomp=unconfined" argument, but the white screen is still there. As with others, downgrading to 6.4.0 makes it work. Is there a solution for the latest version? Thanks for any help. |
Same here, Update to the newest version did this… Take care and have a nice day! |
yeah, same here. @Buba81 |
|
So it's still broken for me at 6.7.1. Still just a white screen. It works at 6.4.0, though. |
|
6.7.1 works fine as long as --security-opt="seccomp=unconfined" is passed and UMASK is removed - on Unraid 6.11.4 |
seccomp=unconfined is incorrect for yml. This sintaxe is for command line docker, i.e. docker run --security-opt seccomp=unconfined [etc]
docker compose --security-opt seccomp=unconfined [etc]The correct sintaxe for yml is: security_opt:
- seccomp:unconfinededit: there is no space in |
|
I had everything working fine until release v6.8.0-ls192. The pull to the release v6.8.0-ls193, two days ago, gave me a permanente blank page. I have many plugins on Calibre. How do I disable them one by one in docker so I could check if some of them is tripping the image? |
it happens for me without any plugins |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This issue is not resolved. I get this white screen regardless what version of the container I run. |
|
please also try incognito mode. somehow i had an issue related with some browser cache. |
|
I too have issues like this. I'm using docker-compose on a synology nas and nothing I do gets me past a black page with a button on the left side. Sometimes (I think when it's even more broken..?) the page stays white, I've had one configuration in which the cursor freezes on a white page too. I've been at this for too long tonight so I'm gonna throw in the towel and describe where I left off here. version: "2.1"
services:
calibre:
image: lscr.io/linuxserver/calibre:6.4.0
container_name: calibre
security_opt:
- seccomp:unconfined #optional
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
#- PASSWORD= #optional
#- CLI_ARGS= #optional
volumes:
- ${DOCKERCONFDIR}/calibre:/config
- ${DOCKERSTORAGEDIR}/media/books:/Calibre_Library
- ${DOCKERCONFDIR}/calibre/upload:/uploads
- ${DOCKERCONFDIR}/calibre/plugins:/plugins
#ports:
#- 8080:8080
#- 8081:8081
#- 3389:3389
#- 3000:3000
restart: unless-stopped
network_mode: "host"
calibre-web:
image: ghcr.io/linuxserver/calibre-web
container_name: calibre-web
environment:
- PUID=${PUID}
- PGID=${PGID}
volumes:
- ${DOCKERCONFDIR}/calibre/calibre-web:/config
- ${DOCKERSTORAGEDIR}/media/books:/books
restart: unless-stopped
depends_on:
- calibre
ports:
- 8083:8083
networks:
- ebooks
networks:
ebooks:
external: trueI tried forwarding all four ports on a separate network for awhile, then I tried simply attaching calibre directly to the host network, no dice here is my .env: I also tried changing the permissions to all of the files and folders to docker:users 777 (probably overkill), completely reinstalling the container in a variety of ways, and using incognito tabs. and here's a pastebin of my logs. |
Version 6 of calibre needs a higher kernel version than many synology NAS are running with. Synology never upgrades the kernel to newer versions of existing models. Not sure which is the lowest supported kernel version, but 3.10 like my synology kernel is not working. You can start a shell inside your container and try to start calibre manualy to look for error messages. |
|
Hey there, I'm having the same blank screen issue on my NAS (not Synology). The kernel is updated regularly and it's using Kernel 5.13, so the new version of calibre should work. Yet, I still get the same qt errors posted above when running calibre inside the docker image: I'm using the Any hints? cheers |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
If anyone on Synology is struggling to get this to work with a Reverse Proxy, try adding the following into Custom Headers: Upgrade : $http_upgrade |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I had what might be a similar issue and found a workaround which I posted here: #104 (comment) |
|
Thanks a lot. Your fix worked for my Synology NAS with kernel version 3.10. I wish the linuxserver team would implement this fix in their build. |
|
This wouldn't be the first time we've seen this with older kernels. It won't be something that we'd apply to our container as while it might fix your issue, it might cause other issues for other users down the line. We could put a note in the readme though or maybe just a general note in our FAQ's. |
|
I am having this issue as well, or at least the same symptom. |
|
This image has been rebased and consolidating connection issues down to #128 |
and others
Expected Behavior
When the container is running,
http://127.0.0.1:8080should serve a functioning guacamole client which can connect to openbox and the calibre desktop interface.Current Behavior
The guacamole interface is blank, with no login screen or list of connections:
Steps to Reproduce
docker-compose.yml:common.envsets:PUIDPGIDTZcalibre-server.envsets:PASSWORDseccomp=unconfinedwas a suggestion I found in issue Calibre 6.0.0 app won't start #91 – the behavior is the same with or without it.Environment
OS:
Debian GNU/Linux 11 (bullseye)Kernel:
Linux 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30)CPU architecture: x86_64
How docker service was installed: via the official docker.com apt repository:
Docker system info
Command used to create docker container (run/create/compose/screenshot)
Using the
docker-compose.ymlpasted above, I simply run:Docker logs
The text was updated successfully, but these errors were encountered: