Artifactory does not reflect a change of the Custom Base URL - artifactory

I installed JFrog Artifactory via Helm. When I first-time log in, I saw the following configuration of URL to File.
The URL has HTTPS and port 80, which is wrong.
Then I configured the Custom Base URL to be correct.
Even if I created a new Maven repo using the quick start wizard, the URL has still port 80 in the path.
The HTTPS protocol and port 80 cause, that the URL is not accessible.
Am I doing something wrong or is it a bug? How to set up the Custom URL to a correct value?
Thank you


The issue was that I forwarded HTTPS traffic to HTTP. It was working but produced the issue described above.
The solution for me was to forward the HTTPS traffic from outside to HTTPS port on the service/artifactory-artifactory-nginx and add the following annotation to the ingress:
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"

Related

How to redirect nginx to another port using proxy settings?

When I go to [myIpAddress:80] in other computers browsers I want to redirect it to localhost:54321 on my server. How to do this?
this is my nginx default file. please complete it to redirect localhost:54321 when I send request to port 80 http port.
Please edit this file and give me the edited configuration.
Check the link below
My Default Nginx Configuration

Forced to use wss:// when behind proxy from https to http

I have setup a nginx proxy to pass https url to internal http neo4j web. I can reach the neo4j login page without any issue, but I am forced to use the neo4j+s/bolt+s interface.
Just wondering how I can configure nginx to remove any ssl related info via proxypass module, in order to login in neo4j with ws, no wss?
Thanks,
Chance

I managed to get rid of wss by adding another nginx proxy to set the https url as upstream server in location.proxy_pass. It won't show wss/neo4j+s/bolt+s any more once you visit the web by the http url. Hopefully it will help for anyone has the similar issue as me.

Rancher 2 disable HTTP to HTTPS redirect

SSL redirect is enabled by default in a Kubernetes NGINX ingress on Rancher 2. We changed the config map and redeployed the nginx -ingres in the system namespace, but the redirect still happens. Has someone managed to disable it?

Unfortunately I don't think you will be able to disable SSL in Rancher v2.
As per Randcher documentation:
For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
You can find there few ways to apply this certs:
Default Rancher-generated Self-signed Certificate
Bring Your Own Certificate, Self-signedlink
Bring Your Own Certificate, Signed by a Recognized CA
Let’s Encrypt Certificatelink
Inside this doc you have hyerlinks to further Rancher docs.
As Rancher by default deploying nginx controller you should also check Rancher docs about Nginx Controller.

As an update, rancher can disable http -> https redirection by disabling ingress's TLS and set a custom header "X-Forwarded-Proto: https" from ingress controller -> rancher,
reference:
https://github.com/rancher/rancher/issues/35088

Forward proxy to redirect HTTPS URL to internal

I'm trying to come up with a solution where I can do the follow:
In my scenario there are 2 servers.
API1: Nginx + API Website
API2: Nginx + Staging Website
In order to check new version of API via mobileapp, I want to set my phone to use a proxy server (Should be API2), and only when the dest URL is https://api.test.com it will redirect it internally to localhost:6000.
Any ideas of how it can be done? I know Nginx does not support SSL Proxing, but maybe I'm wrong.
Thanks

Well,
Eventually I was able to accomplish that by using Apache Traffic Server which has been configured as a forward proxy while doing some map rules to redirect traffic from https to localhost:443/
But, I will be happy to hear some more ideas.
Thanks

Gitlab base url

I'm running Gitlab behind an Apache HTTPD SSL proxy
So, Gitlab is running on http://example.com:80 and my proxy is serving this from https://example.com:443.
Currently when I request password reset emails they provide a link to http://example.com not https://example.com
Does anyone know how to change the base URL to https://example.com while still running the gitlab instance over http?
Thanks,
Adam

Enable https in the gitlab.yml file? https://gitlab.com/gitlab-org/gitlab-ce/blob/dbd88d453b8e6c78a423fa7e692004b1db6ea069/config/gitlab.yml.example#L20

This is now possible.
See: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/nginx.md#supporting-proxied-ssl
Setting nginx['listen_https'] = false should do the trick.

Resources