You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by "soulfulgent (via GitHub)" <gi...@apache.org> on 2026/05/31 19:50:20 UTC
[D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
GitHub user soulfulgent created a discussion: Cannot view vm instance console remotely - site Cannot be reached
Seems i cannot view VM console to my VM instances remotely, however My VMs have internet access and network access
I have "Basic" setup. My guestnetwork has a range of 172.16.0.1 - 172.16.0.100
Configured using my public IP for NATTING. In addition. I created a security group and allowed all for ingress and egress rules and added the group to all VM instances....so allowing ALL access to all ports. I also turned off the firewall on the instance. I assumed traffic would be allowed both ways. The virtual router is Natted and should allow external access, like RDP for my windows servers??
What am I missing?
Anyone run into this issue with Basic setup
Thank you kindly...and I look forward to any help resolving this as soon as possible.
GitHub link: https://github.com/apache/cloudstack/discussions/13295
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "ewerton-silva00 (via GitHub)" <gi...@apache.org>.
GitHub user ewerton-silva00 edited a comment on the discussion: Cannot view vm instance console remotely - site Cannot be reached
@soulfulgent, translate my message from Brazilian Portuguese to your language.
Utilizo o **Nginx** como Proxy Reverso para a **API** do Apache CloudStack, assim como para o **Console Proxy VM** e **Secondary Storage VM**.
Pré-requisitos:
- Mude a porta do Management Server para algo diferente de 8080 (e.g. 8180).
- Dedique um range rede privado exclusivo para SystemVMs
**Passo 01:**
Redireciona todas as requisições para HTTPS:
```
sudo tee /etc/nginx/sites-enabled/default > /dev/null <<EOF
server {
listen 80 default_server;
server_name _;
return 301 https://$host$request_uri;
}
EOF
```
**Passo 02:**
Sobrescreva as configurações padrões do Nginx:
```
sudo tee /etc/nginx/nginx.conf > /dev/null <<EOF
user www-data;
worker_processes auto;
pid /run/nginx.pid;
error_log /var/log/nginx/error.log;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 768;
}
http {
# Basic Settings
sendfile on;
tcp_nopush on;
types_hash_max_size 2048;
server_tokens off;
include /etc/nginx/mime.types;
default_type application/octet-stream;
# SSL Settings
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305;
# Logging Settings
access_log /var/log/nginx/access.log;
# Gzip Settings
gzip on;
gzip_types text/plain text/css application/javascript application/json;
gzip_proxied any;
# Virtual Host Configs
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}
EOF
```
**Passo 03:**
Configuração da API:
```
sudo tee /etc/nginx/sites-available/api.conf > /dev/null <<'EOF'
sudo tee /etc/nginx/sites-available/api.conf > /dev/null <<'EOF'
upstream cloudstack_management {
server 127.0.0.1:8180;
keepalive 32;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name api.suanuvem.io;
ssl_certificate /etc/letsencrypt/live/api.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/api.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/api.access.log main;
error_log /var/log/nginx/api.error.log warn;
if ($cf_proxy = 0) { return 403; }
client_max_body_size 10M;
location ^~ /client/api {
proxy_pass http://cloudstack_management/client/api/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_connect_timeout 30s;
proxy_send_timeout 60s;
proxy_read_timeout 60s;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_buffering off;
proxy_request_buffering off;
}
location / {
return 403;
}
}
EOF
```
**Passo 04:**
Configuração do Secondary Storage VM:
```
server {
listen 443 ssl http2;
server_name ~^(?<oct1>192)-(?<oct2>168)-(?<oct3>0)-(?<oct4>[1-9][0-9]?)\.secstorage\.suanuvem\.io$;
ssl_certificate /etc/letsencrypt/live/secstorage.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/secstorage.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/secstorage.access.log;
error_log /var/log/nginx/secstorage.error.log warn;
if ($oct4 !~ ^(1[0-9]|[2-4][0-9]|50)$) { return 403; }
set $backend_ip "${oct1}.${oct2}.${oct3}.${oct4}";
client_max_body_size 0;
proxy_http_version 1.1;
proxy_cache off;
proxy_request_buffering off;
proxy_max_temp_file_size 0;
proxy_redirect off;
proxy_buffering off;
location / {
proxy_pass https://$backend_ip;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_ssl_verify off;
proxy_read_timeout 600;
}
}
```
Passo 05:
Configuração do Console Proxy VM:
```
server {
listen 443 ssl http2;
listen 8080 ssl http2;
server_name ~^(?<oct1>192)-(?<oct2>168)-(?<oct3>0)-(?<oct4>[1-9][0-9]?)\.consoleproxy\.suanuvem\.io$;
ssl_certificate /etc/letsencrypt/live/consoleproxy.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/consoleproxy.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/consoleproxy.access.log;
error_log /var/log/nginx/consoleproxy.error.log warn;
if ($oct4 !~ ^(1[0-9]|[2-4][0-9]|50)$) { return 403; }
set $backend_ip "${oct1}.${oct2}.${oct3}.${oct4}";
client_max_body_size 0;
proxy_http_version 1.1;
proxy_cache off;
proxy_request_buffering off;
proxy_buffering off;
proxy_max_temp_file_size 0;
proxy_redirect off;
location / {
proxy_pass http://$backend_ip;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 600;
}
location /websockify {
proxy_pass http://$backend_ip:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_cache_bypass $http_upgrade;
proxy_ignore_client_abort off;
proxy_read_timeout 86400;
}
}
```
A acesso a console web das instâncias funciona perfeitamente.
<img width="2555" height="982" alt="image" src="https://github.com/user-attachments/assets/764d149b-4838-4120-990a-56d520918ec0" />
O upload de imagens para o Secondary Storage também funciona perfeitamente.
Espero ter ajudado de alguma forma.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17229308
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "mjstark (via GitHub)" <gi...@apache.org>.
GitHub user mjstark added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
Thanks again for your feedback....
You are still using advanced networking opposed to basic
Most likely you have a block of Public IP's from your provider if your using advanced networking, you cannot use advanced networking with only one public IP from your provider,
my configuration would be different because I have chose basic networking, which relies on security groups and egress rules to allow incoming traffic.
Something I'm don't think I was clear on, further up the conversation. Possibly I miss-understood .., regarding CPVM. I added the IP and port of my CPVM to my physical router. From what I experienced when clicking on **"View console"** from the internet, it opens up showing the IP of the CPVM along with port 8080.
Sharing the screenshot again. Does this look right, should port 8080 be used for CPVM? I already use port 80 externally. Port already mapped to another internal server running a HTTP.
<img width="1650" height="197" alt="image" src="https://github.com/user-attachments/assets/380c4577-9f01-4364-8f32-ff2b0dfc98a3" />
My cloudstack-mgmt server is accessible over the internet using a domain name and a different port, like 9494, for an example
P.S
If anyone has **"console view"** working remotely from the internet using **Basing networking** configuration/mode/model. please share your configuration, hopefully we can do like for like, to see if I'm missing anything.
Greatly appreciate everyone's help with this issue.
Thanks,
Mike
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17359810
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
GitHub user weizhouapache added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
> Thanks again for your feedback....
>
> You are still using advanced networking opposed to basic
>
> Most likely you have a block of Public IP's from your provider if your using advanced networking, you cannot use advanced networking with only one public IP from your provider,
>
> my configuration would be different because I have chose basic networking, which relies on security groups and egress rules to allow incoming traffic.
>
> Something I'm don't think I was clear on, further up the conversation. Possibly I miss-understood .., regarding CPVM. I added the IP and port of my CPVM to my physical router. From what I experienced when clicking on **"View console"** from the internet, it opens up showing the IP of the CPVM along with port 8080.
>
> Sharing the screenshot again. Does this look right, should port 8080 be used for CPVM? I already use port 80 externally. Port already mapped to another internal server running a HTTP.
>
CPVM uses both port 80 (for noVNC UI) and 8080 (for WebSocket).
If you enable SSL, the ports are 443 and 8443. These ports are not configurable.
btw, I think the global setting `consoleproxy.url.domain` should be set to your public IP
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17361093
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "soulfulgent (via GitHub)" <gi...@apache.org>.
GitHub user soulfulgent added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
Thanks for your reply.
Running version 4.22 (forgot to mention)
I agree, the my physical router (provided by ISP) is allowing traffic to my CPVM IP over port 8080. My readings, I found that consoleproxy runs on port 8080. Am I correct in saying this. So currently, my router is allowing traffic from the internet to CPVM over port 8080
First thing, are you saying the CPVM should not be behind a FW in the first place? ..is so, I would need to change/fix this before moving forward. I want to configure this by the book and as it's supposed to work with a basic setup, not by hacks. What are considered best practice for allowing remote access vm instances remotely for a "Basic" setup
Can you please elaborate more on setting up a jump host ..or server/box? in the destination subnet and access the instance console the same ...the same what? Also port forwarding. There are no settings available for port forwarding in Cloudstack UI.
My understanding, to allow vm instances to connect remotely, is controlled by security groups. The security group I created, is configured to "Allow" all ports for CIDR 0.0.0.0./0, representing all ipv4 traffic. With this setup, I should be able to access and/or view server console from the internet?
To add, i don't see any TAB's in cloudstack UI that say "Firewall"
I've added some screenshots for clarity of my setup.
<img width="1224" height="830" alt="defaultGuestNetwork" src="https://github.com/user-attachments/assets/a391b845-3444-4ca8-a227-e2c47224ec84" />
<img width="1337" height="209" alt="systemVM" src="https://github.com/user-attachments/assets/df97b582-d7ea-485c-8cc3-f06dc298693c" />
<img width="1358" height="612" alt="zone" src="https://github.com/user-attachments/assets/f0a51ece-677d-4cd8-88fa-95bda1d5b6aa" />
this is the IP of the VR i get when launching "view console". As mentioned above, the IP has been added to my router/FW
<img width="1650" height="182" alt="console_view_showing_IP" src="https://github.com/user-attachments/assets/9d828465-c361-49f6-a7d0-4411e7e34787" />
Thanks again for your help on this matter. It's greatly appreciated.
Mike
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17160184
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "ewerton-silva00 (via GitHub)" <gi...@apache.org>.
GitHub user ewerton-silva00 added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
@soulfulgent, traduza minha mensagem do Português Brasileiro para o seu idioma.
Utilizo o **Nginx** como Proxy Reverso para a **API** do Apache CloudStack, assim como para o **Console Proxy VM** e **Secondary Storage VM**.
Pré-requisitos:
- Mude a porta do Management Server para algo diferente de 8080 (e.g. 8180).
- Dedique um range rede privado exclusivo para SystemVMs
**Passo 01:**
Redireciona todas as requisições para HTTPS:
```
sudo tee /etc/nginx/sites-enabled/default > /dev/null <<EOF
server {
listen 80 default_server;
server_name _;
return 301 https://$host$request_uri;
}
EOF
```
**Passo 02:**
Sobrescreva as configurações padrões do Nginx:
```
sudo tee /etc/nginx/nginx.conf > /dev/null <<EOF
user www-data;
worker_processes auto;
pid /run/nginx.pid;
error_log /var/log/nginx/error.log;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 768;
}
http {
# Basic Settings
sendfile on;
tcp_nopush on;
types_hash_max_size 2048;
server_tokens off;
include /etc/nginx/mime.types;
default_type application/octet-stream;
# SSL Settings
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305;
# Logging Settings
access_log /var/log/nginx/access.log;
# Gzip Settings
gzip on;
gzip_types text/plain text/css application/javascript application/json;
gzip_proxied any;
# Virtual Host Configs
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}
EOF
```
**Passo 03:**
Configuração da API:
```
sudo tee /etc/nginx/sites-available/api.conf > /dev/null <<'EOF'
sudo tee /etc/nginx/sites-available/api.conf > /dev/null <<'EOF'
upstream cloudstack_management {
server 127.0.0.1:8180;
keepalive 32;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name api.suanuvem.io;
ssl_certificate /etc/letsencrypt/live/api.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/api.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/api.access.log main;
error_log /var/log/nginx/api.error.log warn;
if ($cf_proxy = 0) { return 403; }
client_max_body_size 10M;
location ^~ /client/api {
proxy_pass http://cloudstack_management/client/api/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_connect_timeout 30s;
proxy_send_timeout 60s;
proxy_read_timeout 60s;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_buffering off;
proxy_request_buffering off;
}
location / {
return 403;
}
}
EOF
```
**Passo 04:**
Configuração do Secondary Storage VM:
```
server {
listen 443 ssl http2;
server_name ~^(?<oct1>192)-(?<oct2>168)-(?<oct3>0)-(?<oct4>[1-9][0-9]?)\.secstorage\.suanuvem\.io$;
ssl_certificate /etc/letsencrypt/live/secstorage.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/secstorage.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/secstorage.access.log;
error_log /var/log/nginx/secstorage.error.log warn;
if ($oct4 !~ ^(1[0-9]|[2-4][0-9]|50)$) { return 403; }
set $backend_ip "${oct1}.${oct2}.${oct3}.${oct4}";
client_max_body_size 0;
proxy_http_version 1.1;
proxy_cache off;
proxy_request_buffering off;
proxy_max_temp_file_size 0;
proxy_redirect off;
proxy_buffering off;
location / {
proxy_pass https://$backend_ip;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_ssl_verify off;
proxy_read_timeout 600;
}
}
```
Passo 05:
Configuração do Console Proxy VM:
```
server {
listen 443 ssl http2;
listen 8080 ssl http2;
server_name ~^(?<oct1>192)-(?<oct2>168)-(?<oct3>0)-(?<oct4>[1-9][0-9]?)\.consoleproxy\.suanuvem\.io$;
ssl_certificate /etc/letsencrypt/live/consoleproxy.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/consoleproxy.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/consoleproxy.access.log;
error_log /var/log/nginx/consoleproxy.error.log warn;
if ($oct4 !~ ^(1[0-9]|[2-4][0-9]|50)$) { return 403; }
set $backend_ip "${oct1}.${oct2}.${oct3}.${oct4}";
client_max_body_size 0;
proxy_http_version 1.1;
proxy_cache off;
proxy_request_buffering off;
proxy_buffering off;
proxy_max_temp_file_size 0;
proxy_redirect off;
location / {
proxy_pass http://$backend_ip;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 600;
}
location /websockify {
proxy_pass http://$backend_ip:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_cache_bypass $http_upgrade;
proxy_ignore_client_abort off;
proxy_read_timeout 86400;
}
}
```
A acesso a console web das instâncias funciona perfeitamente.
<img width="2555" height="982" alt="image" src="https://github.com/user-attachments/assets/764d149b-4838-4120-990a-56d520918ec0" />
O upload de imagens para o Secondary Storage também funciona perfeitamente.
Espero ter ajudado de alguma forma.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17229308
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "soulfulgent (via GitHub)" <gi...@apache.org>.
GitHub user soulfulgent added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
Hey Rajujith,
You still willing to help me? This is most likely a common problem when using basic networking and accessing VM's from internet, safe to assume
Let me know if you need any **additional info** on my setup to assist you. All firewalls are disabled on instances
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17199545
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "ewerton-silva00 (via GitHub)" <gi...@apache.org>.
GitHub user ewerton-silva00 added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
Perhaps this will help.
- Use Nginx as a reverse proxy.
- My CloudStack environment uses an Advanced Zone.
This is my configuration:
`
server {
listen 443 ssl http2;
listen 8080 ssl http2;
server_name ~^(?<oct1>192)-(?<oct2>168)-(?<oct3>0)-(?<oct4>[1-9][0-9]?)\.consoleproxy\.mydomain\.io$;
ssl_certificate /etc/letsencrypt/live/consoleproxy.mydomain.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/consoleproxy.mydomain.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/consoleproxy.access.log;
error_log /var/log/nginx/consoleproxy.error.log warn;
if ($oct4 !~ ^(1[0-9]|[2-4][0-9]|50)$) { return 403; }
set $backend_ip "${oct1}.${oct2}.${oct3}.${oct4}";
client_max_body_size 0;
proxy_http_version 1.1;
proxy_cache off;
proxy_request_buffering off;
proxy_buffering off;
proxy_max_temp_file_size 0;
proxy_redirect off;
location / {
proxy_pass http://$backend_ip;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 600;
}
location /websockify {
proxy_pass http://$backend_ip:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_cache_bypass $http_upgrade;
proxy_ignore_client_abort off;
proxy_read_timeout 86400;
}
}
`
**Note**:
The Management Server port needs to be changed to something other than 8080.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17339868
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "rajujith (via GitHub)" <gi...@apache.org>.
GitHub user rajujith edited a comment on the discussion: Cannot view vm instance console remotely - site Cannot be reached
@soulfulgent Your web client needs connectivity to the Console Proxy VM(CPVM) Public IP , port 80 to view the instance consoles. Since the CPVM IP is behind a NAT you could run a jump host in the destination subnet and access the Instance console using the same or avoid using NAT or use Port forwarding.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17130065
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "rajujith (via GitHub)" <gi...@apache.org>.
GitHub user rajujith added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
@soulfulgent Your client needs connectivity to the Console Proxy VM(CPVM) Public IP , port 80 to view the instance consoles. Since the CPVM IP is behind a NAT you could run a jump host in the destination subnet and access the Instance console using the same or avoid using NAT or use Port forwarding.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17130065
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "mjstark (via GitHub)" <gi...@apache.org>.
GitHub user mjstark added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
My desktop is on the same network (172.16.0.0) and I have no problem to "view console" ...I'm talking remotely as from over the internet.
I'm not sure I understand you? regarding cloudstack VR not being in the path for instances of Systems VMs. Are you talking about the path in my browser that pops up when clicking on "view console" As you can see (highlighted in RED), when I launch "view console",
It shows the virtual router IP **172.16.0.95 and port 8080**, which belongs to the GuestNetwork range of IP's. I've added this IP and PORT to my physical router to allow incoming on port 8080 of VR IP.
<img width="1650" height="197" alt="image" src="https://github.com/user-attachments/assets/e948bd35-0ab2-4cfc-aa17-35be51521faa" />
The GuestNetwork is configured using a Source NAT ip address, Public IP to be assigned to the public interface. This is my static IP from my provider that is assigned to my physical router.
<img width="406" height="499" alt="source_NAT" src="https://github.com/user-attachments/assets/f3ed4d73-dc26-4233-b39d-ca021c5c81a6" />
So bottom line, I have cloudstack working, I can upload ISO's and create intances from them. The instances have access outbound, but not inbound traffic ...Just to reiterate, my INGRESS rules for my security groups assigned to my vm instances are allowing all incoming traffic to CIDR 0.0.0.0/0
From my understanding, the way I have configured base networking, based on the documentation, that the INGRESS rules of the security groups dictate the incoming traffic, in addition with adding the VR IP and port to my physical router.
I appreciate your help. Please get back to me as soon as you can. I would like to get this working. Been trying to get this working for over 1 month now.
Thanks again, greatly appreciated Rajujith ....please get back to be as soon as you can.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17244724
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "mjstark (via GitHub)" <gi...@apache.org>.
GitHub user mjstark added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
Can I get a reply on my response.
If you have inbound traffic working with Basic networking (allowing access remotely from internet) and with your GuestNetwork configured with Source NAT address (Public IP from provider assigned to physical router) and my security group with ingress rules allowing all, can you provide me how exactly you have your Cloudstack configured. Keep in mind, not by work-arounds or hacks only by the whitepapers/docs from Apache ...If you had to configure some workaround or hack to get it working, than this would be a bug.
Looking forward to your reply.
Thanks,
Mike
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17293910
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "ewerton-silva00 (via GitHub)" <gi...@apache.org>.
GitHub user ewerton-silva00 deleted a comment on the discussion: Cannot view vm instance console remotely - site Cannot be reached
@soulfulgent, translate my message from Brazilian Portuguese to your language.
Utilizo o **Nginx** como Proxy Reverso para a **API** do Apache CloudStack, assim como para o **Console Proxy VM** e **Secondary Storage VM**.
Pré-requisitos:
- Mude a porta do Management Server para algo diferente de 8080 (e.g. 8180).
- Dedique um range rede privado exclusivo para SystemVMs
**Passo 01:**
Redireciona todas as requisições para HTTPS:
```
sudo tee /etc/nginx/sites-enabled/default > /dev/null <<EOF
server {
listen 80 default_server;
server_name _;
return 301 https://$host$request_uri;
}
EOF
```
**Passo 02:**
Sobrescreva as configurações padrões do Nginx:
```
sudo tee /etc/nginx/nginx.conf > /dev/null <<EOF
user www-data;
worker_processes auto;
pid /run/nginx.pid;
error_log /var/log/nginx/error.log;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 768;
}
http {
# Basic Settings
sendfile on;
tcp_nopush on;
types_hash_max_size 2048;
server_tokens off;
include /etc/nginx/mime.types;
default_type application/octet-stream;
# SSL Settings
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305;
# Logging Settings
access_log /var/log/nginx/access.log;
# Gzip Settings
gzip on;
gzip_types text/plain text/css application/javascript application/json;
gzip_proxied any;
# Virtual Host Configs
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}
EOF
```
**Passo 03:**
Configuração da API:
```
sudo tee /etc/nginx/sites-available/api.conf > /dev/null <<'EOF'
sudo tee /etc/nginx/sites-available/api.conf > /dev/null <<'EOF'
upstream cloudstack_management {
server 127.0.0.1:8180;
keepalive 32;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name api.suanuvem.io;
ssl_certificate /etc/letsencrypt/live/api.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/api.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/api.access.log main;
error_log /var/log/nginx/api.error.log warn;
if ($cf_proxy = 0) { return 403; }
client_max_body_size 10M;
location ^~ /client/api {
proxy_pass http://cloudstack_management/client/api/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_connect_timeout 30s;
proxy_send_timeout 60s;
proxy_read_timeout 60s;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_buffering off;
proxy_request_buffering off;
}
location / {
return 403;
}
}
EOF
```
**Passo 04:**
Configuração do Secondary Storage VM:
```
server {
listen 443 ssl http2;
server_name ~^(?<oct1>192)-(?<oct2>168)-(?<oct3>0)-(?<oct4>[1-9][0-9]?)\.secstorage\.suanuvem\.io$;
ssl_certificate /etc/letsencrypt/live/secstorage.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/secstorage.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/secstorage.access.log;
error_log /var/log/nginx/secstorage.error.log warn;
if ($oct4 !~ ^(1[0-9]|[2-4][0-9]|50)$) { return 403; }
set $backend_ip "${oct1}.${oct2}.${oct3}.${oct4}";
client_max_body_size 0;
proxy_http_version 1.1;
proxy_cache off;
proxy_request_buffering off;
proxy_max_temp_file_size 0;
proxy_redirect off;
proxy_buffering off;
location / {
proxy_pass https://$backend_ip;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_ssl_verify off;
proxy_read_timeout 600;
}
}
```
Passo 05:
Configuração do Console Proxy VM:
```
server {
listen 443 ssl http2;
listen 8080 ssl http2;
server_name ~^(?<oct1>192)-(?<oct2>168)-(?<oct3>0)-(?<oct4>[1-9][0-9]?)\.consoleproxy\.suanuvem\.io$;
ssl_certificate /etc/letsencrypt/live/consoleproxy.suanuvem.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/consoleproxy.suanuvem.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/consoleproxy.access.log;
error_log /var/log/nginx/consoleproxy.error.log warn;
if ($oct4 !~ ^(1[0-9]|[2-4][0-9]|50)$) { return 403; }
set $backend_ip "${oct1}.${oct2}.${oct3}.${oct4}";
client_max_body_size 0;
proxy_http_version 1.1;
proxy_cache off;
proxy_request_buffering off;
proxy_buffering off;
proxy_max_temp_file_size 0;
proxy_redirect off;
location / {
proxy_pass http://$backend_ip;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 600;
}
location /websockify {
proxy_pass http://$backend_ip:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_cache_bypass $http_upgrade;
proxy_ignore_client_abort off;
proxy_read_timeout 86400;
}
}
```
A acesso a console web das instâncias funciona perfeitamente.
<img width="2555" height="982" alt="image" src="https://github.com/user-attachments/assets/764d149b-4838-4120-990a-56d520918ec0" />
O upload de imagens para o Secondary Storage também funciona perfeitamente.
Espero ter ajudado de alguma forma.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17229308
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
GitHub user weizhouapache added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
> **_Anyone willing to help_** ,...OR am I in the wrong channel to get support on configurations issues/questions???
@mjstark
There are several discussions on how to set up a reverse proxy (such as Nginx or HAProxy) for the CPVM.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17334972
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
GitHub user weizhouapache added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
> You probably meant advanced networking, the zone should be core ...I'm using Basic networking, since I only have one public IP. Internally I'm NATTED, using 172.16.0.0/16
@mjstark
if you want to access the "VM Console", you need to configure the public access to the CPVM, which provides the console service for virtual machines.
You do not need to configure anything on the virtual machines themselves. In other words, neither the zone type (Basic or Advanced) nor the guest network type (Isolated or Shared) has any effect on the console access.
please read again what @ewerton-silva00 shared.
If you want to access a Windows VM via RDP, you obviously need to allow incoming traffic on port 3389.
However, if the Windows VM does not have a public IP address, it is your responsibility to provide public access to the VM, for example by assigning a public IP and configuring the necessary firewall/NAT rules, or by using a VPN.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17348395
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "mjstark (via GitHub)" <gi...@apache.org>.
GitHub user mjstark added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
I certainly appreciate your response Ewerton,
You probably meant advanced networking, the zone should be core ...I'm using Basic networking, since I only have one public IP. Internally I'm NATTED, using 172.16.0.0/16
Quick look at my setup;
H/W physical;
KVM1 - 172.16.6.1
KVM2 - 172.16.6.2
KVM3 - 172.16.6.3
MGMT - 172.16.6.4
Management traffic - range
172.16.0.1 - 172.16.0.50
Zone GuestNetwork - range (Also configure with Source NAT IP addressing)
172.16.0.51 - 172.16.0.150
Gateway
172.16.1.254
Egress/Ingress Rules
Allow All for CIDR 0.0.0.0/0
That being said. Following the documentation. Egress rules from your security groups are supposed to allow for "Console view" to work along with incoming traffic, say I want to RDP into a windows instance over port 3389 from the internet. I don't believe Cloudstack, was designed to go to that extreme to get incoming traffic to work. If so, if surely would have been documented in their guides/whitepapers. Seems these are all work-arounds, instead of getting to work like the app should, ...the way it's documented.
Even other blogs state that the security group egress rules are all you need, as long as you add the virtual router to your physical router and allow all incoming. In my case, my virtual router is 172.16.0.95
**Since you are using Advanced networking, this won't work for me.
I'm looking for someone who has incoming traffic working with Basic networking. Would like to review their setup**
Thanks again for your help,
Mike
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17346001
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "ewerton-silva00 (via GitHub)" <gi...@apache.org>.
GitHub user ewerton-silva00 edited a comment on the discussion: Cannot view vm instance console remotely - site Cannot be reached
Perhaps this will help.
- Use Nginx as a reverse proxy.
- My CloudStack environment uses an Advanced Zone.
This is my configuration:
```
server {
listen 443 ssl http2;
listen 8080 ssl http2;
server_name ~^(?<oct1>192)-(?<oct2>168)-(?<oct3>0)-(?<oct4>[1-9][0-9]?)\.consoleproxy\.mydomain\.io$;
ssl_certificate /etc/letsencrypt/live/consoleproxy.mydomain.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/consoleproxy.mydomain.io/privkey.pem;
ssl_dhparam /etc/ssl/dhparam.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Content-Type-Options nosniff always;
add_header X-Frame-Options DENY always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
access_log /var/log/nginx/consoleproxy.access.log;
error_log /var/log/nginx/consoleproxy.error.log warn;
if ($oct4 !~ ^(1[0-9]|[2-4][0-9]|50)$) { return 403; }
set $backend_ip "${oct1}.${oct2}.${oct3}.${oct4}";
client_max_body_size 0;
proxy_http_version 1.1;
proxy_cache off;
proxy_request_buffering off;
proxy_buffering off;
proxy_max_temp_file_size 0;
proxy_redirect off;
location / {
proxy_pass http://$backend_ip;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 600;
}
location /websockify {
proxy_pass http://$backend_ip:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_cache_bypass $http_upgrade;
proxy_ignore_client_abort off;
proxy_read_timeout 86400;
}
}
```
**Note**:
The Management Server port needs to be changed to something other than 8080.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17339868
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "ewerton-silva00 (via GitHub)" <gi...@apache.org>.
GitHub user ewerton-silva00 added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
> I certainly appreciate your response Ewerton,
>
> You probably meant advanced networking, the zone should be core ...I'm using Basic networking, since I only have one public IP. Internally I'm NATTED, using 172.16.0.0/16
>
> Quick look at my setup; H/W physical; KVM1 - 172.16.6.1 KVM2 - 172.16.6.2 KVM3 - 172.16.6.3 MGMT - 172.16.6.4
>
> Management traffic - range 172.16.0.1 - 172.16.0.50
>
> Zone GuestNetwork - range (Also configure with Source NAT IP addressing) 172.16.0.51 - 172.16.0.150
>
> Gateway 172.16.1.254
>
> Egress/Ingress Rules Allow All for CIDR 0.0.0.0/0
>
> That being said. Following the documentation. Egress rules from your security groups are supposed to allow for "Console view" to work along with incoming traffic, say I want to RDP into a windows instance over port 3389 from the internet. I don't believe Cloudstack, was designed to go to that extreme to get incoming traffic to work. If so, if surely would have been documented in their guides/whitepapers. Seems these are all work-arounds, instead of getting to work like the app should, ...the way it's documented.
>
> Even other blogs state that the security group egress rules are all you need, as long as you add the virtual router to your physical router and allow all incoming. In my case, my virtual router is 172.16.0.95
>
> **Since you are using Advanced networking, this won't work for me.
>
> I'm looking for someone who has incoming traffic working with Basic networking. Would like to review their setup**
>
> Thanks again for your help, Mike
I also only have one public IPv4 address.
My entire environment is on a private network with CIDR 192.168.0.0/24.
My environment isn't very different from yours, and yet I can still access the instance consoles externally, as well as upload and download from the Secondary Storage VM.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17351765
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "mjstark (via GitHub)" <gi...@apache.org>.
GitHub user mjstark added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
I'm blowing away the database and starting over by running the "cloudstack-setup-databases" with --force -recreate
I'm configuring with "Advanced Networking", it seems the proposed choice. Will let you know how this works out.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17379881
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "soulfulgent (via GitHub)" <gi...@apache.org>.
GitHub user soulfulgent added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
..adding another image. Showing the view console for win2025 instance.
<img width="1014" height="182" alt="view_console" src="https://github.com/user-attachments/assets/28597d26-6e73-422b-a5ec-db8296be7a62" />
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17160204
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "mjstark (via GitHub)" <gi...@apache.org>.
GitHub user mjstark added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
**_Anyone willing to help_** ,...OR am I in the wrong channel to get support on configurations issues/questions???
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17334045
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "ewerton-silva00 (via GitHub)" <gi...@apache.org>.
GitHub user ewerton-silva00 added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
> Thanks again for your feedback....
>
> You are still using advanced networking opposed to basic
>
> Most likely you have a block of Public IP's from your provider if your using advanced networking, you cannot use advanced networking with only one public IP from your provider,
>
> my configuration would be different because I have chose basic networking, which relies on security groups and egress rules to allow incoming traffic.
>
> Something I'm don't think I was clear on, further up the conversation. Possibly I miss-understood .., regarding CPVM. I added the IP and port of my CPVM to my physical router. From what I experienced when clicking on **"View console"** from the internet, it opens up showing the IP of the CPVM along with port 8080.
>
> Sharing the screenshot again. Does this look right, should port 8080 be used for CPVM? I already use port 80 externally. Port already mapped to another internal server running a HTTP.
> <img alt="image" width="1650" height="197" src="https://private-user-images.githubusercontent.com/18348953/610233533-380c4577-9f01-4364-8f32-ff2b0dfc98a3.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODE4NzAzNjMsIm5iZiI6MTc4MTg3MDA2MywicGF0aCI6Ii8xODM0ODk1My82MTAyMzM1MzMtMzgwYzQ1NzctOWYwMS00MzY0LThmMzItZmYyYjBkZmM5OGEzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjE5VDExNTQyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM1ZWE5N2FlZWQ1OGI1ODM1N2JjMjRlMjZiNzJlMTJiZWFkNDBmMGZkODZhYjZmZjE3YTkyOTZhMzNhZDQwMWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9._BDi2Cg0afHGcZjR-ZcxyNooI3-_2vbTpi2T4tXYNX4">
>
> My cloudstack-mgmt server is accessible over the internet using a domain name and a different port, like 9494, for an example
>
> P.S If anyone has **"console view"** working remotely from the internet using **Basing networking** configuration/mode/model. please share your configuration, hopefully we can do like for like, to see if I'm missing anything.
>
> Greatly appreciate everyone's help with this issue.
>
> Thanks, Mike
I don't have a block of public IPs.
I only have one public IPv4 address.
The configuration I described above works perfectly.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17364231
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "rajujith (via GitHub)" <gi...@apache.org>.
GitHub user rajujith added a comment to the discussion: Cannot view vm instance console remotely - site Cannot be reached
In a basic zone you are using a shared guest Network in CloudStack, the CloudStack virtual router is not in the data path for instances of SystemVMs. Please make sure the Console Proxy VM IP on port 80 is reachable from your desk. CloudStack itself is not blocking anything.
GitHub link: https://github.com/apache/cloudstack/discussions/13295#discussioncomment-17231440
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] Cannot view vm instance console remotely - site Cannot be reached [cloudstack]
Posted by "soulfulgent (via GitHub) via users" <us...@cloudstack.apache.org>.
GitHub user soulfulgent closed a discussion: Cannot view vm instance console remotely - site Cannot be reached
Seems i cannot view VM console to my VM instances remotely, however My VMs have internet access and network access
I have "Basic" setup. My guestnetwork has a range of 172.16.0.1 - 172.16.0.100
Configured using my public IP for NATTING. In addition. I created a security group and allowed all for ingress and egress rules and added the group to all VM instances....so allowing ALL access to all ports. I also turned off the firewall on the instance. I assumed traffic would be allowed both ways. The virtual router is Natted and should allow external access, like RDP for my windows servers??
What am I missing?
Anyone run into this issue with Basic setup
Thank you kindly...and I look forward to any help resolving this as soon as possible.
GitHub link: https://github.com/apache/cloudstack/discussions/13295
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org