cluster : c31a8621-fa9d-4f35-a0d5-a33102769557
host : 1c-psql
port : 1541
name : "Local cluster"
Ошибка установки соединения
по причине:
server_addr=1c-psql descr=11001(0x00002AF9): Этот хост неизвестен. line=580 file=src\core\src\Networking.cpp
server {
server_name cr.domain.com;
location / {
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_connect_timeout 10000;
proxy_send_timeout 10000;
proxy_read_timeout 10000;
send_timeout 10000;
client_max_body_size 1000m;
proxy_pass http://172.16.10.157:5050;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/cr.domain.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/cr.domain.com/privkey.pem; # managed by Certbot
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
}
server {
listen 80;
server_name cr.domain.com;
return 301 https://$server_name$request_uri;
}server {
listen 80;
server_name reg.domain.com;
return 301 https://$server_name$request_uri;
}
server {
server_name reg.domain.com;
location / {
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_connect_timeout 10000;
proxy_send_timeout 10000;
proxy_read_timeout 10000;
send_timeout 10000;
client_max_body_size 1000m;
proxy_pass http://172.16.10.157;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/reg.domain.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/reg.domain.com/privkey.pem; # managed by Certbot
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
}external_url = 'https://reg.domain.com'
nginx['listen_port'] = 80
nginx['listen_https'] = false
nginx['proxy_set_headers'] = {
"Host" => "$http_host",
"X-Real-IP" => "$remote_addr",
"X-Forwarded-For" => "$proxy_add_x_forwarded_for",
"X-Forwarded-Proto" => "https",
"X-Forwarded-Ssl" => "on"
}
registry_external_url 'https://cr.domain.com'
gitlab_rails['registry_enabled'] = true
gitlab_rails['gitlab_host'] = 'reg.domain.com'
gitlab_rails['registry_host'] = 'cr.domain.com'
registry['token_realm'] = 'https://reg.domain.com'
#registry['registry_http_addr'] = "127.0.0.1:5000"
registry['enable'] = true
registry_nginx['enable'] = true
registry_nginx['proxy_set_headers'] = {
"Host" => "$http_host",
"X-Real-IP" => "$remote_addr",
"X-Forwarded-For" => "$proxy_add_x_forwarded_for",
"X-Forwarded-Proto" => "https",
"X-Forwarded-Ssl" => "on"
}
registry_nginx['listen_port'] = 5050
registry_nginx['listen_https'] = falselocation / {
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_connect_timeout 10000;
proxy_send_timeout 10000;
proxy_read_timeout 10000;
send_timeout 10000;
client_max_body_size 1000m;
## proxy_redirect off;
# proxy_set_header X-Forwarded-Host $host;
# proxy_set_header X-Forwarded-Server $host;
# proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
## proxy_set_header X-Forwarded-Proto https;
## proxy_set_header Host $http_host;
## proxy_set_header X-Real-IP $remote_addr;
## proxy_set_header X-Forwarded-Ssl on;
# proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_set_header X-Forwarded-Proto $scheme;
# proxy_headers_hash_max_size 512;
# proxy_headers_hash_bucket_size 128;
# proxy_cache off;
# proxy_buffering off;
# proxy_request_buffering off;
## proxy_http_version 1.1;
proxy_pass 172.16.10.157:5050;
}
external_url = 'https://reg.domain.com'
nginx['listen_port'] = 80
nginx['listen_https'] = false
#nginx['proxy_protocol'] = true
#nginx['real_ip_trusted_addresses'] = [ "127.0.0.0/8", "172.16.10.150/32"]
nginx['proxy_set_headers'] = {
# "X-Forwarded-Proto" => "$scheme",
# "X-Forwarded-Proto" => "http",
"CUSTOM_HEADER" => "VALUE"
}
registry_external_url = 'https://cr.domain.com:5050'
registry['enable'] = true
#registry_nginx['enable'] = true
#registry_nginx['proxy_set_headers'] = {
# "Host" => "$http_host",
# "X-Real-IP" => "$remote_addr",
# "X-Forwarded-For" => "$proxy_add_x_forwarded_for",
# "X-Forwarded-Proto" => "http",
# "X-Forwarded-Ssl" => "on",
# "X-Forwarded-Proto" => "$scheme"
# }
registry_nginx['listen_port'] = 5050
#registry_nginx['listen_https'] = false
### Settings used by GitLab application
gitlab_rails['registry_enabled'] = true
gitlab_rails['registry_host'] = "cr.domain.com"
gitlab_rails['registry_port'] = "5050"
gitlab_rails['registry_path'] = "/var/opt/gitlab/gitlab-rails/shared/registry"
#gitlab_rails['registry_api_url'] = "cr.domain.com:5000"
registry['registry_http_addr'] = "127.0.0.1:5000"
#nginx['redirect_http_to_https'] = true
#registry_nginx['redirect_http_to_https'] = true
#mattermost_nginx['redirect_http_to_https'] = true
Error response from daemon: Get https://cr.domain.com:5050/v2/: Get /jwt/auth?account=root&client_id=docker&offline_token=true&service=container_registry: unsupported protocol scheme ""
172.16.10.150 - - [04/Sep/2022:07:16:07 +0000] "GET /v2/ HTTP/1.0" 401 87 "" "docker/20.10.7 go/go1.13.8 git-commit/20.10.7-0ubuntu5~18.04.3 kernel/4.15.0-112-generic os/linux arch/amd64 UpstreamClient(Docker-Client/20.10.7 \x5C(linux\x5C))" -
Для примера:
ping -M do 77.88.55.242 -s 500
PING 77.88.55.242 (77.88.55.242) 500(528) bytes of data.
508 bytes from 77.88.55.242: icmp_seq=1 ttl=249 time=8.88 ms
Это важно ?
С самого роутера со стороны OVPN сервера всё четко - если я пингую с него то ответ такого же размера как запрос.