General Assistance: Secure Connection Failed - login URL

[Azy83]

Hi,
I tried to use "localhost:8081" and "127.0.0.1:8081" on my FireFox, but I had a hard time finding the correct URL to see the login page. Can you please provide me some suggestions?

Thank you,
Azy

[SRAPSpencer]

The .env file in your VECTR directory determines with URL VECTR is accessible at. It must be configured and have DNS setup for the hostname appropriate to your environment.

[Telecnope]

Hello,

I'm having the same problem, I'm currently trying to set up this vectr server, but I'm getting a pseudo SSL error.
So I tried to fill my /etc/hosts to have name resolution but again same error.

Can anyone help me?

(I don't have a DNS server on my network)

[Telecnope]

Hello,

I'm having the same problem, I'm currently trying to set up this vectr server, but I'm getting a pseudo SSL error. So I tried to fill my /etc/hosts to have name resolution but again same error.

Can anyone help me?

(I don't have a DNS server on my network)

I've just tried a manipulation that consisted in adding a line, but it had no effect: “VECTR_FEATURES_SSLCONF=FALSE”.

[doodleincode]

Hello,

I'm having the same problem, I'm currently trying to set up this vectr server, but I'm getting a pseudo SSL error. So I tried to fill my /etc/hosts to have name resolution but again same error.

Can anyone help me?

(I don't have a DNS server on my network)

If you are using the default generated cert, this cert is self-signed and by design untrusted by the browser. The generated cert covers the host/domain name that you provided as the VECTR_HOSTNAME value in the .env file. Make sure that you are accessing VECTR using the hostname.

Assuming the above is true, you should be able to tell the browser to accept the risk of trusting the self-signed cert.

[Telecnope]

Hello,
I'm having the same problem, I'm currently trying to set up this vectr server, but I'm getting a pseudo SSL error. So I tried to fill my /etc/hosts to have name resolution but again same error.
Can anyone help me?
(I don't have a DNS server on my network)

If you are using the default generated cert, this cert is self-signed and by design untrusted by the browser. The generated cert covers the host/domain name that you provided as the VECTR_HOSTNAME value in the .env file. Make sure that you are accessing VECTR using the hostname.

Assuming the above is true, you should be able to tell the browser to accept the risk of trusting the self-signed cert.

Hello,

I managed to solve my problem.
I had to modify the file /etc/hosts :
XXX.XXX.XXX.XXX vectr

Thanks to this line, then by searching in HTTPS://vectr:8081 it worked.

Then for the connection, you just need to pay attention to the timestamp of the machine in relation to the server. It tolerates a one-minute difference (compared with UTC time).

Good configuration

[ishdube]

Anyone found a solution to this? issue. My /etc/hosts is correctly configured and all services are running.

[SRAPSpencer]

Anyone found a solution to this? issue. My /etc/hosts is correctly configured and all services are running.

Are you having the same issue in the screenshot with the SSL Internal Error Alert? If so Please check your Caddy Gateway logs and post them here.

If not please open a new issue with the specifics of your deployment and error you're receiving.

[ishdube]

Update: I changed the hostname back to the default on the env instead of localhost and the error cleared and all works fine.

Are you having the same issue in the screenshot with the SSL Internal Error Alert? If so Please check your Caddy Gateway logs and post them here.

If not please open a new issue with the specifics of your deployment and error you're receiving.

The issue is the same as in the image/screenshot above.. I have attached the logs. I changed the VECTR_HOSTNAME to localhost on the .env file and I am accessing Vectr on the local machine.

caddy_gateway_logs.txt