troke12 commented on issue #7317:
URL: https://github.com/apache/cloudstack/issues/7317#issuecomment-1493393323
> > > > 3. But only port 8080 that cannot listen when i setting to `https`
scheme inside nginx, tried to check the port 8080 from nginx it's not used by
nginx, but still not working
> > >
> > >
> > > @troke12
> > > Have you tried my suggestion in previous comment ?
> > > Do not use "location /"
> >
> >
> > Yes, I only set to /websockify, but still not working
>
> @troke12 can you share the nginx setting ? I was able to access the
console in my testing
sure, here the settings
```nginx
server {
listen 80;
listen [::]:80;
server_name console.mydomain.id;
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name console.mydomain.id;
#Certificate pathes
ssl_certificate /etc/letsencrypt/live/npm-7/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/npm-7/privkey.pem;
ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH";
ssl_protocols TLSv1.2;
ssl_prefer_server_ciphers on;
client_max_body_size 3584K;
location / {
proxy_pass https://172.16.25.31;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
}
}
server {
listen 8080 ssl;
listen [::]:8080 ssl;
server_name console.mydomain.id;
#Certificate pathes
ssl_certificate /etc/letsencrypt/live/npm-7/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/npm-7/privkey.pem;
ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH";
ssl_protocols TLSv1.2;
ssl_prefer_server_ciphers on;
client_max_body_size 3584K;
location /pop {
add_header Content-Type text/plain;
return 200 'gangnam style!';
}
location /websockify {
proxy_pass https://172.16.25.31:8080;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
}
}
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
