this post was submitted on 08 Apr 2024
15 points (75.9% liked)

Programming

17326 readers
185 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
15
Access unrestricted remote desktop from very restricted office network (lemmy.world)
submitted 7 months ago by disconnectikacio@lemmy.world to c/programming@programming.dev
14 comments fedilink hide all child comments
 

I want to access an unrestricted desktop at home (preferably a docker novnc desktop container), from the very restricted office laptop/network.

The foundations are clear, started a docker container with novnc access published the porst, forwarded the required ports on my router, and i can access it from outside using my phone, or my own laptop, but can't from the office.

The novnc landing page loads, but the connection to remote desktop fails, probably because the websockets connections are also blocked in office, so only the plain http(s) accesses are allowed (not even RDP is allowed).

(Not even dyndns providers are allowed, but i can note my current ip address in my phone :D )

Ofc i barely can install anything on office laptop, so i can create fe openvpn tunnel, etc...

Do you have some hints if it can be solved?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] cm0002@lemmy.world 5 points 7 months ago (1 children)

Was about to post to use Guacamole too, web sockets will work over HTTPS, OP is likely trying to do websockets over another port that's getting blocked.

But over HTTPS with Guac should be fine because I did this exact thing on a very locked down work network

[โ€“] NightEagle@lemmy.world 1 points 7 months ago* (last edited 7 months ago)

Some proxies block Websocket Connections by default for unknown URLs, even for port 443. Don't ask me how I know :D