Closed srikanth-reddy-m closed 5 years ago
Issue-Label Bot is automatically applying the label #bug
to this issue, with a confidence of 0.94. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
This issue is solved, I have missed roxy_set_header X-Forwarded-Proto 'https' header setting in nginx. If we are using nginx as a reverse proxy with https we have to add this header to flask-app builder to know schema information.
@srikanth-reddy-m Do you have problem when selecting the datasource?
@syazwan0913 This worked for me.
# superset/config.py
ENABLE_PROXY_FIX = True
PROXY_FIX_CONFIG = {"x_for": 1, "x_proto": 1, "x_host": 1, "x_port": 1, "x_prefix": 1
@maltoze what is the version of superset you are using?
@syazwan0913 I'm using 0.29.
I also change this in my code.
# superset/__init__.py
if app.config.get("ENABLE_PROXY_FIX"):
from werkzeug.middleware.proxy_fix import ProxyFix
app.wsgi_app = ProxyFix(app.wsgi_app, **app.config.get("PROXY_FIX_CONFIG"))
related #8117
@maltoze alright I got it. Thanks
I am using superset ver 0.36 and having the same problem when i create an api get user info below
i have used all solutions of you but it don't work :(. Someone help me , thanks all
@CaptainHoangLe are you using Nginx? can share your configuration?
@CaptainHoangLe are you using Nginx? can share your configuration?
Dear bro ,this is my config nginx
You need to add this line inside your Nginx config
proxy_set_header X-Forwarded-Proto https;
Also in superset_config.py
you must enable this:
ENABLE_PROXY_FIX = True
PROXY_FIX_CONFIG = {"x_for": 1, "x_proto": 1, "x_host": 1, "x_port": 1, "x_prefix": 1
You need to add this line inside your Nginx config
proxy_set_header X-Forwarded-Proto https;
Also in
superset_config.py
you must enable this:ENABLE_PROXY_FIX = True PROXY_FIX_CONFIG = {"x_for": 1, "x_proto": 1, "x_host": 1, "x_port": 1, "x_prefix": 1
i have just done that but it can't help me to sloving this problem .i don't know where the error came from
it send request to https but response location is http
@CaptainHoangLe are you using Nginx? can share your configuration?
Dear bro ,this is my config nginx
Have you try to run without proxy_set_header X-Forwarded-For $remote_addr
and proxy_set_header Host $http_host
?
Because mine having same problem as yours if using that config.
@CaptainHoangLe are you using Nginx? can share your configuration?
Dear bro ,this is my config nginx
Have you try to run without
proxy_set_header X-Forwarded-For $remote_addr
andproxy_set_header Host $http_host
?Because mine having same problem as yours if using that config.
i have tried but nothing changed. Can i see your nginx config? thanks
Here is my working nginx config
worker_processes auto;
error_log /var/log/nginx/error.log error;
events {
worker_connections 1024;
}
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] $status '
'"$request" $body_bytes_sent "$http_referer" '
'"$http_user_agent"';
access_log /var/log/nginx/access.log main;
client_header_timeout 3m;
client_body_timeout 3m;
send_timeout 3m;
client_header_buffer_size 1k;
large_client_header_buffers 4 4k;
gzip on;
gzip_min_length 1100;
gzip_buffers 4 8k;
gzip_types text/plain;
output_buffers 1 32k;
postpone_output 1460;
sendfile on;
tcp_nopush on;
tcp_nodelay on;
client_max_body_size 200M;
server_tokens off;
add_header X-Frame-Options SAMEORIGIN;
add_header X-Content-Type-Options nosniff;
add_header X-XSS-Protection "1; mode=block";
upstream backend {
server IP;
}
server {
listen 80;
server_name _;
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
server_name analytics.local;
ssl_certificate /etc/nginx/ssl/ssl.crt;
ssl_certificate_key /etc/nginx/ssl/ssl.key;
underscores_in_headers on;
location / {
proxy_http_version 1.1;
proxy_set_header Connection "";
proxy_read_timeout 300s;
proxy_connect_timeout 300s;
proxy_send_timeout 300s;
proxy_pass http://backend;
proxy_max_temp_file_size 0;
}
}
}
Here is my working nginx config
worker_processes auto; error_log /var/log/nginx/error.log error; events { worker_connections 1024; } http { include /etc/nginx/mime.types; default_type application/octet-stream; log_format main '$remote_addr - $remote_user [$time_local] $status ' '"$request" $body_bytes_sent "$http_referer" ' '"$http_user_agent"'; access_log /var/log/nginx/access.log main; client_header_timeout 3m; client_body_timeout 3m; send_timeout 3m; client_header_buffer_size 1k; large_client_header_buffers 4 4k; gzip on; gzip_min_length 1100; gzip_buffers 4 8k; gzip_types text/plain; output_buffers 1 32k; postpone_output 1460; sendfile on; tcp_nopush on; tcp_nodelay on; client_max_body_size 200M; server_tokens off; add_header X-Frame-Options SAMEORIGIN; add_header X-Content-Type-Options nosniff; add_header X-XSS-Protection "1; mode=block"; upstream backend { server IP; } server { listen 80; server_name _; return 301 https://$server_name$request_uri; } server { listen 443 ssl; server_name analytics.local; ssl_certificate /etc/nginx/ssl/ssl.crt; ssl_certificate_key /etc/nginx/ssl/ssl.key; underscores_in_headers on; location / { proxy_http_version 1.1; proxy_set_header Connection ""; proxy_read_timeout 300s; proxy_connect_timeout 300s; proxy_send_timeout 300s; proxy_pass http://backend; proxy_max_temp_file_size 0; } } }
thank you, i got it. this reason is config in nginx not apply when i change.Once again I thank you very much for your help
A clear and concise description of what the bug is.
CodeBase: Master Branch
When trying to change superset data source from HTTPS it is trying to open Url in HTTP in which it is creating the error.
Error: Unsafe attempt to load URL, Domains, protocols, and ports must match
Expected results
It should load URL's with only HTTps what you expected to happen.
Actual results
what actually happens.
Screenshots
![supersetImage](
)
If applicable, add screenshots to help explain your problem.
How to reproduce the bug
Environment
(please complete the following information):
superset version
python --version
node -v
npm -v
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
Additional context
Add any other context about the problem here.