Configured HTTPS, got: ERR_INVALID_HTTP_RESPONSE

SCM-Manager
1

Hello everyone,

I’m currently running Ubuntu 20.04 LTS along with SCM-Manager 2.40.1. I’ve followed the documentation to set up HTTPS, but when I try to access it, it initially just loads indefinitely. After granting read permission to everyone for the keystore.pkcs, I now receive the ERR_INVALID_HTTP_RESPONSE error. However, at least now I can see the following in the logs (i’m showing just what i think may be relevant, especially the last three INFO logs):

WARNING: Multiple Servlet injectors detected. This is a warning indicating that you have more than one GuiceFilter running in your web application. If this is deliberate, you may safely ignore this message. If this is NOT deliberate however, your application may not work as expected.

INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@1a84a8b2{/,[file:///opt/scm-server/var/webapp/docroot/],AVAILABLE}

INFO:oejs.AbstractConnector:main: Started ServerConnector@e45f292{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}

INFO:oejus.SslContextFactory:main: x509=X509@17354708(1,h=[technoleaderscm.ddns.net],a=,w=) for Server@134c38[provider=null,keyStore=file:///opt/scm-server/conf/keystore.pkcs12,trustStore=null]

INFO:oejs.AbstractConnector:main: Started ServerConnector@25a65b77{SSL, (ssl, http/1.1)}{0.0.0.0:8443}

INFO:oejs.Server:main: Started @5753ms

The last three lines of the log indicate that the server seems to be functioning on https, but I still can’t access it. Any suggestions would be greatly appreciated.

Thanks in advance for your help.

3

Hey @abanob.azzer ,

can you please double check that you tried to access https://localhost:8443/scm ?

I’m getting the ERR_INVALID_HTTP_RESPONSE when I’m trying to access the page with http instead of https.

If this is not the issue, we have to take a closer look.

Regards
René

(By the way: I don’t find a version 2.40.1. Do you mean 2.41.1?)

4

You’re right, my fault. I don’t know how I missed that; I assumed there was an ‘https’ prefix, and indeed, it works. And yes, I meant that version. Thank you for pointing it out!

5

Glad to hear this, thanks for the feedback :slight_smile: