# Configured HTTPS, got: ERR\_INVALID\_HTTP\_RESPONSE

**URL:** <https://community.cloudogu.com/t/configured-https-got-err-invalid-http-response/1305>\
**Category:** SCM-Manager (General)\
**Created:** [April 4, 2024, 5:42pm UTC](https://community.cloudogu.com/t/configured-https-got-err-invalid-http-response/1305 "2024-04-04T17:42:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![abanob.azzer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/abanob.azzer/32/1391_2.png) [@abanob.azzer](https://community.cloudogu.com/u/abanob.azzer)\
**Post date:** [April 4, 2024, 5:42pm UTC](https://community.cloudogu.com/t/configured-https-got-err-invalid-http-response/1305/1 "2024-04-04T17:42:09Z")

</div>

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](http://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.

---

<div class="post-metadata">

**Author:** ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)\
**Post date:** [April 11, 2024, 1:52pm UTC](https://community.cloudogu.com/t/configured-https-got-err-invalid-http-response/1305/3 "2024-04-11T13:52:14Z")

</div>

Hey @abanob.azzer ,

can you please double check that you tried to access [https://localhost:8443/scm](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?)

---

<div class="post-metadata">

**Author:** ![abanob.azzer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/abanob.azzer/32/1391_2.png) [@abanob.azzer](https://community.cloudogu.com/u/abanob.azzer)\
**Post date:** [April 11, 2024, 2:32pm UTC](https://community.cloudogu.com/t/configured-https-got-err-invalid-http-response/1305/4 "2024-04-11T14:32:52Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)\
**Post date:** [April 12, 2024, 6:54am UTC](https://community.cloudogu.com/t/configured-https-got-err-invalid-http-response/1305/5 "2024-04-12T06:54:16Z")

</div>

Glad to hear this, thanks for the feedback 🙂
