error code 403 - forbidden

[mrs...@gmail.com]

We suddenly got this error in our SCM 1.60 (we are installing version 2 on a new setup as we speak, but need the old 1.60 until we are ready for migration)

HTTP ERROR 403

Problem accessing /. Reason:

Forbidden 

We started renewing certificates, but not sure this is the reason as the certificate looks fine for the website. 
We restored the entire server to make sure it wasn't the new certificate that was the issue. But with a 3 day earlier backup we see the same error.

Anyone got a hint/ clue that we can work on? has file-permissions suddenly changed somewhere by accident by someone.

Merry christmas everyone. 

[9thSense]

How'd it go?

--
You received this message because you are subscribed to the Google Groups "scmmanager" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scmmanager/6bd1c868-cda2-4390-9e66-278fd022dd04n%40googlegroups.com.

--

Stephanie Smith

520-288-1079

______________

[mrs...@gmail.com]

Still the same problem - we tried to disable HTTPS and use normal HTTP 8080 and we still get the same error 403 forbidden.

Something has changed for sure, just no clue of what it can be. Will try to look at file permissions, if someone changed those.

[mrs...@gmail.com]

checking /var/logs/scm/scm-server.err we have a lot of these. - not sure if this leads to anything though.

2020-12-28 13:37:30.493:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet

2020-12-28 13:37:30.507:INFO:oejsh.ContextHandler:started o.e.j.w.WebAppContext{/,file:/var/cache/scm/work/webapp/},/opt/scm-server/var/webapp/scm-webapp.war

2020-12-28 13:37:30.831:INFO:oejus.SslContextFactory:Enabled Protocols [TLSv1.2, TLSv1.1, TLSv1] of [TLSv1.3, TLSv1.2, TLSv1.1, TLSv1, SSLv3, SSLv2Hello]

2020-12-28 13:37:30.843:INFO:oejs.AbstractConnector:Started SslSelectCha...@0.0.0.0:443

2020-12-28 13:44:07.335:INFO:oejs.Server:Graceful shutdown SslSelectCha...@0.0.0.0:443

2020-12-28 13:44:07.335:INFO:oejs.Server:Graceful shutdown o.e.j.w.WebAppContext{/,file:/var/cache/scm/work/webapp/},/opt/scm-server/var/webapp/scm-webapp.war

2020-12-28 13:44:09.357:INFO:oejsh.ContextHandler:stopped o.e.j.w.WebAppContext{/,file:/var/cache/scm/work/webapp/},/opt/scm-server/var/webapp/scm-webapp.war

2020-12-28 13:44:10.603:INFO:oejs.Server:jetty-7.6.21.v20160908

[9thSense]

Your tesseract is collapsing? gracefully

To view this discussion on the web visit https://groups.google.com/d/msgid/scmmanager/b837da62-b32d-492b-aa3b-7df3f0402e6bn%40googlegroups.com.

[Sebastian Sdorra]

Hi,

The log you posted does not show any error message. It looks like a normal start and shutdown of the embedded jetty. Do you get the error 403 only on the root path (https://yourserver/)? What happens if you open https://yourserver/scm?

Sebastian

To view this discussion on the web visit https://groups.google.com/d/msgid/scmmanager/CA%2BSjGAhqzswZrPxMtQgQUQnMwKjHGsXjo0AQdyFOouGqChEjLg%40mail.gmail.com.

[mrs...@gmail.com]

Hi Sebastian,

I gave up and only had one option left, to remove scm and then reinstall it and that seemed to work. I am not quite sure why the service had stopped at gave us the 403 forbidden error. My focus is now to migrate everything to our new SCM 2.8 version. Just need to find the best method on how to migrate our 1500 HG and GIT repositories. - trying to search through your website for guide on this.

[Sebastian Sdorra]

The best way for the migration is to use our migration wizard. For such a size of repositories you have to tune jetty settings to get the migration to work. Please have a look at https://www.scm-manager.org/docs/2.12.x/en/migrate-scm-manager-from-v1/

If you have questions about the migration, feel free to ask.

Sebastian

To view this discussion on the web visit https://groups.google.com/d/msgid/scmmanager/eca6bd0d-06a6-46fc-8ebf-5b323d68d1fen%40googlegroups.com.