[OSGeo] #3248: Cannot login into staging trac

Committees SAC tickets
1

#3248: Cannot login into staging trac
---------------------------+-----------------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III (strk)
Component: SysAdmin/Trac | Keywords:
---------------------------+-----------------------------------------------
When I try going to https://dev.trac.osgeo.org/osgeo/login I get the
error: `The page isn’t redirecting properly`
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3248&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

2

#3248: Cannot login into staging trac
-------------------------+-------------------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III
Component: | (strk)
  SysAdmin/Trac | Resolution:
Keywords: | Relationships:
-------------------------+-------------------------------------------------
Comment (by strk):

I found out about this problem while trying to test the cross-reference
plugin asked for in #2105 (and this is a test for that :slight_smile:
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3248#comment:1&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

3

#3248: Cannot login into staging trac
--------------------------+------------------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III (strk)
Component: | Resolution:
  SysAdmin/Trac |
Keywords: |
--------------------------+------------------------------------------------
Comment (by robe):

As mentioned on matrix, it looks like tracsvn-dev is set to use production
ldap.osgeo.org so you shouldn't be having issues logging in related to
ldap.

Also I can log in fine via OSGeo Git Services: Gitea - Git with a cup of tea

I vaguely recall there being some crazy https redirect issues we had I
forget how we fixed that but possibly was only fixed on production. I'd
check the osgeo4-nginx config for dev.trac.osgeo.org as well as the apache
config in tracsvn-dev.
--
Ticket URL: <#3248 (Cannot login into staging trac) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

4

#3248: Cannot login into staging trac
--------------------------+------------------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III (strk)
Component: | Resolution:
  SysAdmin/Trac |
Keywords: |
--------------------------+------------------------------------------------
Comment (by strk):

This is another case in which having the ansible service role ALSO deploy
to the http-proxy sounds like a sensible thing to do (like I was proposing
in https://git.osgeo.org/gitea/sac/ansible-deployment/pulls/61 for Gitea
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3248#comment:3&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

5

#3248: Cannot login into staging trac
--------------------------+------------------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2024-III (strk)
Component: | Resolution: fixed
  SysAdmin/Trac |
Keywords: |
--------------------------+------------------------------------------------
Changes (by strk):

* status: new => closed
* resolution: => fixed

Comment:

The problem was fixed by proxying to https instead of http:
{{{
diff --git a/etc/nginx/sites-available/dev.trac.osgeo.org b/etc/nginx
/sites-available/dev.trac.osgeo.org
index 278a9af..9bef7b4 100644
--- a/etc/nginx/sites-available/dev.trac.osgeo.org
+++ b/etc/nginx/sites-available/dev.trac.osgeo.org
@@ -21,7 +21,7 @@ server {
                  }
                  client_max_body_size 0;
                  include /etc/nginx/proxy_protocol_params;
- proxy_pass http://tracsvn-dev.lxd;
+ proxy_pass https://tracsvn-dev.lxd;
                  proxy_redirect off;
          }
}}}

This was already https in production.
I'll see about deploying these proxy configs via ansible too
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3248#comment:4&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

6

#3248: Cannot login into staging trac
--------------------------+------------------------------------------------
Reporter: strk | Owner: strk
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2024-III (strk)
Component: | Resolution: fixed
  SysAdmin/Trac |
Keywords: |
--------------------------+------------------------------------------------
Comment (by strk):

For the record, this is the commit fixing the redirect loop:
https://git.osgeo.org/gitea/sac/osgeo4-nginx/commit/437ba1c0bb00cfb79da7444092135fca658a087e
--
Ticket URL: <#3248 (Cannot login into staging trac) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.