harbor login with 404 #18851
Unanswered
storehubdeploy
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Please check the env EXT_ENDPOINT in your harbor-core container?
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I set up the harbor in k8s cluster with version v1.10.17, i can login in the UI dashbord, but i use docker command login will get eorr!
the error info:
any suggestion about this issue?
this is harbor nginx config:
worker_processes auto;
pid /tmp/nginx.pid;
events {
worker_connections 1024;
use epoll;
multi_accept on;
}
http {
client_body_temp_path /tmp/client_body_temp;
proxy_temp_path /tmp/proxy_temp;
fastcgi_temp_path /tmp/fastcgi_temp;
uwsgi_temp_path /tmp/uwsgi_temp;
scgi_temp_path /tmp/scgi_temp;
tcp_nodelay on;
this is necessary for us to be able to disable request buffering in all cases
proxy_http_version 1.1;
upstream core {
server harbor-harbor-core;
}
upstream portal {
server harbor-harbor-portal;
}
log_format timed_combined '[$time_local]:$remote_addr - '
'"$request" $status $body_bytes_sent '
'"$http_referer" "$http_user_agent" '
'$request_time $upstream_response_time $pipe';
access_log /dev/stdout timed_combined;
server {
listen 8080;
server_tokens off;
# disable any limits to avoid HTTP 413 for large image uploads
client_max_body_size 0;
location /service/notifications {
return 404;
}
}
}
Beta Was this translation helpful? Give feedback.
All reactions