Blank page instead of startup screen #2186
Comments
|
I also have the same issue with docker version... Hm |
|
Thanks for the report. We will have a Look
aunicorn111 ***@***.***> schrieb am Mo., 24. Juli 2023, 17:10:
… I also have the same issue with docker version... Hm
—
Reply to this email directly, view it on GitHub
<#2186 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AL7ASPVWKETK5UFBOFRNFRDXR2F7VANCNFSM6AAAAAA2VNV33M>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Hi, I have the exact same issue on 2.45.0 / 2.45.1 Debian host. I created a ticket on the community site but just registered on Github to file a bug report here. Logs posted on the community link, but I can mirror the data here if it helps: https://community.cloudogu.com/t/blank-page-on-fresh-scm-server-2-45-1-install-debian-host/1202 |
|
Just to be sure i don't miss anything. You did start your server somewhat like that?:
|
|
If your question is directed to me, I have done an install of the .deb in my Debian host (Bullseye and also tried Bookworm) and used systemctl start scm-server to get scm-server to run. I can manually stop scm-server, re-start it and I still get a blank page when logging in. The process is loaded and there are no systemctl errors.
If I "downgrade" to 2.44, then everything works as expected. |
|
I will try to reproduce your error with an debian machine. We had several issues releasing version 2.45.0 and therefore recommend using version 2.45.1 instead. |
|
I have 2.45.1 installed and also tried 2.45.0 , both result in a blank page on login. |
|
Could you please check your network- and console tab in your browser? Does any kind of frontend error occur? |
|
I can guarantee that it is not a network or console issue. Why? Because I can apt-purge scm-server and manually install the .DEB for 2.44.2 and can immediately log in. No other change to the server or desktop. I see no observable front-end issues. The only "noteworthy" comment in the scm-server log is I have tried clearing history, caches, etc and am using Firefox and Chrome and ran them with ZERO extentions. I have set up numerous versions of scm-server in the past with ZERO issues. Please see my cloudogu community posting for logs and history of debugging. |
|
I have tried Docker and Debian installations. Both worked for me with version 2.45.1.... I'll do some research to see what has actually changed since version 2.44.2. Sorry for the inconvenience.
|
|
Are you doing a Debian install on a machine that previously had scm-server and/or data already present? I am trying on a new setup which has no prior scm-server install. |
|
Freshly installed, not an upgrade. Just to be sure. You have not modified your server-config.xml nor does any kind of reverse proxy is used on this machine? Also: You cannot see the initialization page where you should insert your startup token? |
Which Debian image did you install? I have tried amd64/Bullseye & amd64/Bookworm but I can try to do a completely clean install on another machine. |
|
I tried our debian docker image and addinationally installed the debian package on my own ubuntu machine following our instructions. |
|
May I respectfully ask you try installing the .DEB on a Debian host and not Ubuntu to try and re-produce? You can even try in an lxc / lxd container to avoid a new machine setup. I can try also in an Ubuntu container to see if that makes any difference. Which Ubuntu version are you using? |
|
I will try amd64/bookworm with the .DEB. My machine is running: Ubuntu 22.04.2 LTS (Jammy Jellyfish) |
|
You may run into a bug with ca-certificates and Java, suggest you try amd64/Bullseye for now. I tried installing 2.45.1 in an Ubuntu/Jammy in an lxc based container and experience same issue. Note: I looked into dev tools and do see this, perhaps this is an http / https issue? 
|
|
Yes, this could be the issue. Do you use the |
|
For me the issue resolved by installing ver 2.44.1 >.> |
|
Not sure if I should close the issue or not since the problem stays with ver 2.45.x 👀 |
|
1). Apologies on missing your suggestion to check network & console in the browser, I thought you meant general network issues Is scm-server (jetty?) automatically re-directing to use https by default now? This sounds like a circular problem if on 2.45.x http has been deprecated but if the scm-server instance hasn't been set up to use https. Note : If I want to move to https, I would set this up in the reverse proxy (nginx) and not in scm-server. 
|
|
@vrreg We have not upgraded jetty (yet) and i could not figure out why it is not working for you guys. Unfortunately it works on my machines... I will ask a colleague to try to reproduce it. If you want to try https with SCMM please find our documentation here. BTW: I could not make Bullseye work. Could you provide a command to start Bullseye as a docker container? Another wild guess: Have you tried to connect to port |
I have a Debian Bullseye host(physical computer, not virtual or container) and I create a new "container" using :
I then answer 'debian', 'bullseye', 'amd64' . You can also try 'ubuntu', 'jammy', 'amd64' as an lxc-container. Note: lxc / lxd (like Docker) can use dnsmasq and/or alter your networking setup (bridge, tunnels, etc) so installing lxc or lxd should be done with some caution if this is a main development machine. |
|
We can finally reproduce this error on a bookworm machine. We assume that installing the Thanks for your help and patience. I will get back too you soon. |
|
The errors were really confusing but we found the culprit. With SCM-Manager version < 2.45.0 we added more strict security headers. One of them is this Content security header: Upgrade-Insecure-Requests, which seems only to work on Debian and therefore this error could not be reproduced on other platforms. We will remove this security header and release a new version 2.45.2 asap. Again thanks for the report. |
|
Thank you and the SCM team so much for working on resolution so quickly! |
|
Hey, version 2.45.2 was just released and we tested it for debian. Hopefully it should work again for everyone. |
|
Confirmed that 2.45.2 fixes the issue, login page comes up properly on a new Debian setup! THANK YOU!! |
Hello! Stumbled upon an issue: I have a blank page whenever I try to connect to scm-manager via firefox browser. Don't think the issue is in the browser since I used scm-manager before and it worked fine with firefox. Log info also didn't help much...
Here are the logs.
The text was updated successfully, but these errors were encountered: