Custom Query (296 matches)

Often jenkins switches from https to http when clicking an url. Examples:

• Go to this URL → click on "Document" (next to the big sign) → you are redirected to http instead of https
• Go to this URL → click login (upper right corner) → enter invalid account → you are redirected to http instead of https

Also login doesn't always work (or only after closing and opening the website again).

I see that jenkins is started with these command-line arguments:

--httpPort=8080
--httpListenAddress=127.0.0.1

According to ​https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins it may be possible to use these arguments instead:

--httpPort=-1 (disable http)
--httpsPort=8443
--httpsListenAddress=127.0.0.1

After that, the apache configuration to redirect /jenkins to localhost:8080 should be changed to redirect to localhost:8443.

Maybe this solves the issue.

We must migrate the LDAP directory in the new server to adapt to the final domain name!

In order to test the domain change (.info → .net) we could do something:

1. Add orxonox.net as a hostname entry in the new server, pointing to localhost.
2. Change our working stations DNS resolutions of www.orxonox.net to point to the new server whenever we are working on it.
3. Make all the changes in the configuration, and test this way.

It might be a way to make the migration more "transparent" to the users, or reduce the bunch of time that the old services are down.

This way we could spread the migration in time a bit more (i.e: no need to shut down everyithing for one entire week)

If we would add therese entries in my local resolv.conf to point to the new server's IP… it would work. I haven't tested it though.