[Support] Djoss - PuTTY

[givmedew]

I've tried setting this like others have instructed and when I hit connect in putty its just a blank console with the blinking green cursor.  I'm on a Supermicro X9SRL-F based board.  I have (2) serial ports... I have tried connecting both.  I am trying to connect to an Arista managed switch.  I've connected to this switch through windows using a USB to Serial but I lost the USB to Serial cable so I am trying to connect to the switch with my server since it has a real serial port and I have tons of these serial management cables.

Edited September 16, 2021 by givmedew

[Djoss]

On 9/16/2021 at 6:01 PM, givmedew said:

I've tried setting this like others have instructed and when I hit connect in putty its just a blank console with the blinking green cursor.  I'm on a Supermicro X9SRL-F based board.  I have (2) serial ports... I have tried connecting both.  I am trying to connect to an Arista managed switch.  I've connected to this switch through windows using a USB to Serial but I lost the USB to Serial cable so I am trying to connect to the switch with my server since it has a real serial port and I have tons of these serial management cables.

Which settings are you using in PuTTY to connect?

[Masterwishx]

need help to put putty behind reverce proxy using NPM ,

copied cloudflare cert to putty but cant accesss to site putty.mysite.com 

also authelia is used in proxy ...

Edited February 5, 2022 by Masterwishx

[Masterwishx]

i have this on screen (too many redirection)

 

 

 

 

 

 

also having authelia setting in Advanced in Nginx Proxy Manager should i add somethink else ?

 

#NPM Proxy Logs to one file for goaccess monitoring
access_log /config/logs/proxy_logs.log proxy;
error_log /config/log/proxy_errors.log warn;

 

location /authelia {
internal;
set $upstream_authelia http://192.168.0.199:9091/api/verify;
proxy_pass_request_body off;
proxy_pass $upstream_authelia;    
proxy_set_header Content-Length "";

# Timeout if the real server is dead
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;
client_body_buffer_size 128k;
proxy_set_header Host $host;
proxy_set_header X-Original-URL $scheme://$http_host$request_uri;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr; 
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $http_host;
proxy_set_header X-Forwarded-Uri $request_uri;
proxy_set_header X-Forwarded-Ssl on;
proxy_redirect  http://  $scheme://;
proxy_http_version 1.1;
proxy_set_header Connection "";
proxy_cache_bypass $cookie_session;
proxy_no_cache $cookie_session;
proxy_buffers 4 32k;

send_timeout 5m;
proxy_read_timeout 240;
proxy_send_timeout 240;
proxy_connect_timeout 240;
}

location / {
set $upstream_putty $forward_scheme://$server:$port;
proxy_pass $upstream_putty;

auth_request /authelia;
auth_request_set $target_url https://$http_host$request_uri;
auth_request_set $user $upstream_http_remote_user;
auth_request_set $email $upstream_http_remote_email;
auth_request_set $groups $upstream_http_remote_groups;
proxy_set_header Remote-User $user;
proxy_set_header Remote-Email $email;
proxy_set_header Remote-Groups $groups;

error_page 401 =302 https://auth.mysite.com/?rd=$target_url;

client_body_buffer_size 128k;

proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

send_timeout 5m;
proxy_read_timeout 360;
proxy_send_timeout 360;
proxy_connect_timeout 360;

proxy_set_header Host $host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection upgrade;
proxy_set_header Accept-Encoding gzip;
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 X-Forwarded-Host $http_host;
proxy_set_header X-Forwarded-Uri $request_uri;
proxy_set_header X-Forwarded-Ssl on;
proxy_redirect  http://  $scheme://;
proxy_http_version 1.1;
proxy_set_header Connection "";
proxy_cache_bypass $cookie_session;
proxy_no_cache $cookie_session;
proxy_buffers 64 256k;

set_real_ip_from 172.18.0.0/16;
set_real_ip_from 172.19.0.0/16;
real_ip_header CF-Connecting-IP;
real_ip_recursive on;

}
 

also using cloudflare i copyied 2 files from NPM cert to putty (web-fullchain.pem,web-privkey.pem),

also have secure connection enabled ..

what should i do for make putty work behind reverse proxy ?

 

 

Edited February 8, 2022 by Masterwishx

[Masterwishx]

33 minutes ago, Masterwishx said:

i have this on screen (too many redirection)

 

 

 

 

also having authelia setting in Advanced in Nginx Proxy Manager should i add somethink else ?

 

#NPM Proxy Logs to one file for goaccess monitoring
access_log /config/logs/proxy_logs.log proxy;
error_log /config/log/proxy_errors.log warn;

 

location /authelia {
internal;
set $upstream_authelia http://192.168.0.199:9091/api/verify;
proxy_pass_request_body off;
proxy_pass $upstream_authelia;    
proxy_set_header Content-Length "";

# Timeout if the real server is dead
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;
client_body_buffer_size 128k;
proxy_set_header Host $host;
proxy_set_header X-Original-URL $scheme://$http_host$request_uri;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr; 
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $http_host;
proxy_set_header X-Forwarded-Uri $request_uri;
proxy_set_header X-Forwarded-Ssl on;
proxy_redirect  http://  $scheme://;
proxy_http_version 1.1;
proxy_set_header Connection "";
proxy_cache_bypass $cookie_session;
proxy_no_cache $cookie_session;
proxy_buffers 4 32k;

send_timeout 5m;
proxy_read_timeout 240;
proxy_send_timeout 240;
proxy_connect_timeout 240;
}

location / {
set $upstream_putty $forward_scheme://$server:$port;
proxy_pass $upstream_putty;

auth_request /authelia;
auth_request_set $target_url https://$http_host$request_uri;
auth_request_set $user $upstream_http_remote_user;
auth_request_set $email $upstream_http_remote_email;
auth_request_set $groups $upstream_http_remote_groups;
proxy_set_header Remote-User $user;
proxy_set_header Remote-Email $email;
proxy_set_header Remote-Groups $groups;

error_page 401 =302 https://auth.mysite.com/?rd=$target_url;

client_body_buffer_size 128k;

proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

send_timeout 5m;
proxy_read_timeout 360;
proxy_send_timeout 360;
proxy_connect_timeout 360;

proxy_set_header Host $host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection upgrade;
proxy_set_header Accept-Encoding gzip;
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 X-Forwarded-Host $http_host;
proxy_set_header X-Forwarded-Uri $request_uri;
proxy_set_header X-Forwarded-Ssl on;
proxy_redirect  http://  $scheme://;
proxy_http_version 1.1;
proxy_set_header Connection "";
proxy_cache_bypass $cookie_session;
proxy_no_cache $cookie_session;
proxy_buffers 64 256k;

set_real_ip_from 172.18.0.0/16;
set_real_ip_from 172.19.0.0/16;
real_ip_header CF-Connecting-IP;
real_ip_recursive on;

}
 

also using cloudflare i copyied 2 files from NPM cert to putty (web-fullchain.pem,web-privkey.pem),

also have secure connection enabled ..

what should i do for make putty work behind reverse proxy ?

 

 

 

 

also added but still nothing...

 

location /websockify {
        proxy_pass  $upstream_putty;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection upgrade;
        proxy_read_timeout 86400;
    }

[Djoss]

When behind NPM, putty container doesn't handle any certificate.  Certificates are handled by NPM.

 

So when using default settings for the putty container (no need to enable sure connection), your proxy host configuration should have Forward IP set to the unRAID IP and the Forward Port set to 7816.  You also need to enable "WebSockets Support".

 

[Masterwishx]

8 hours ago, Djoss said:

When behind NPM, putty container doesn't handle any certificate.  Certificates are handled by NPM.

 

Thanks its Working, also i cant find where to put private key for connection ?

[Djoss]

2 hours ago, Masterwishx said:

 

Thanks its Working, also i cant find where to put private key for connection ?

Which connection are you talking about ?

[Masterwishx]

4 hours ago, Djoss said:

Which connection are you talking about ?

ssh

[Masterwishx]

On 2/10/2022 at 2:28 PM, Djoss said:

Which connection are you talking about ?

 

I was unable to find auth where we need to put privet.key for server connect in ssh section ,

but after changed docker to bridge and then back to custom proxynet all option in ssh section is now avalible ...

[Djoss]

Yeah I fixed the issue, but looks like I forgot to provide an update here ...

[Masterwishx]

in Latest version when connect button pressed the Putty is Disconnected.

 

 

 

[Djoss]

2 hours ago, Masterwishx said:

in Latest version when connect button pressed the Putty is Disconnected.

 

 

 

 

Are you connecting using an existing profile ?

[Masterwishx]

2 hours ago, Djoss said:

Are you connecting using an existing profile ?

 

Do you mean ssh profile from version befor ? Yes

[Djoss]

6 minutes ago, Masterwishx said:

Do you mean ssh profile from version befor ? Yes

 

The problem seems to be related to the font used.  Did you change it the the profile ?  Can you try to edit the profile and see what is configured ?

 

Not sure why it gives an error now, since nothing related to that changed from the last version...

 

[Masterwishx]

Yes the problem was in both ssh profile fonts : 

server:-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1

 

Edited January 7, 2023 by Masterwishx

[Masterwishx]

On 1/5/2023 at 7:46 PM, Djoss said:

Not sure why it gives an error now,

 

I think changed in profiles in some previse version

Fixed by changed to monospace

[Djoss]

Ok great, thanks for the update!