Hey, not sure if you ever got this functioning. Had recently got my hands on some PiKVM 4Plus and ran into the same issue. In my case the PiKVM is being run behind and Nginx Reverse Proxy.
My issues were:
- no webterm ( you'd click on the option after login, redirected and you just get the reconnect option but never connects)
- no stream options( reset stream option grayed out with no mpeg/h.264 options present)
- no ATX option
- no drive option
- ethernet icon blinking orange and status: connecting...
got a hint from this question https://github.com/pikvm/pikvm/issues/1081
checked the config for my jellyfin instance; Had the second half that mentioned upgrading to web socket protocol and applied as follows:
restarted nginx and was able to access all the PiKVM functionalities behind my fqdn![:D]( "Very Happy")
My issues were:
- no webterm ( you'd click on the option after login, redirected and you just get the reconnect option but never connects)
- no stream options( reset stream option grayed out with no mpeg/h.264 options present)
- no ATX option
- no drive option
- ethernet icon blinking orange and status: connecting...
got a hint from this question https://github.com/pikvm/pikvm/issues/1081
checked the config for my jellyfin instance; Had the second half that mentioned upgrading to web socket protocol and applied as follows:
restarted nginx and was able to access all the PiKVM functionalities behind my fqdn
Code:
server {server_name server.locallocation /{proxy_pass https://pi.kvm.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;# Upgrade to WebSocket protocol when requestedproxy_set_header Upgrade $http_upgrade;proxy_set_header Connection "Upgrade";}}Statistics: Posted by feintdoxx — Sun Mar 10, 2024 2:40 pm