-
-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Description
I am trying to adapt the oath2 component to strava.
My streamlit app is served on port 3475 and forwarded usin nginx reverse proxy as follows:
server {
listen 5443 ssl;
server_name run.duckdns.org;
ssl_certificate /etc/letsencrypt/live/run.duckdns.org/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/run.duckdns.org/privkey.pem;
ssl_dhparam /etc/ssl/certs/dhparam.pem;
location / {
proxy_pass http://0.0.0.0:3475/;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
}}
server {
listen 80;
server_name run.duckdns.org;
location / {
proxy_pass http://localhost:3475/;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
I also noticed that the button component uses port 3000 though I already have a service running on port 3000.
I was wondering what should be my redirect URI and it it the same as defined here i.e. in my case https://run.duckdns.org:5443/component/streamlit_oauth.authorize_button? because I get: "redirect_uri","code":"invalid"
Metadata
Metadata
Assignees
Labels
No labels