More > JRiver Media Center 26 for Linux
Docker Container for JRiver Media Center 26
max096:
That's the log from x11vnc. Does not look like he guessed your password though. But also does not look like your firewall rules are working if you are still getting that after you applied them.
One thing you can do in the container is enable secure connection. That will enable https and ssl in vnc. Ofc it wont really solve the problem of it being world viewable if you make it public. If you dont need to access vnc when not at home then don't foward 5800 and 5900 from your router to your NAS.
Id recommend looking into setting up a VPN to you home network and don't expose any ports of any services otherwise. The less gates you open the less you are gonna get annoyed by them.
Another good way to do it if you need public accessability without a VPN would be haproxy. Ive not looked into it that much yet. But Ive seen this https://forum.level1techs.com/t/haproxy-wi-run-lots-of-public-services-on-your-home-server/159335 recently. Looked very interesting.
max096:
--- Quote from: bob on August 03, 2020, 05:24:50 pm ---I have no idea why you are seeing that but if the docker container ethernet interface is running in bridged mode you can't block it by changing the firewall on the device it's running on (the DS1819+ I assume) .
You could run a firewall in the container or block it on your outside router.
I'm suspicious that you are seeing response packets to something originating from within the container itself.
--- End quote ---
Not sure how you come to the conclusion that a connection is established from within the container to the outside?
bob:
--- Quote from: max096 on August 04, 2020, 07:19:35 am ---Not sure how you come to the conclusion that a connection is established from within the container to the outside?
--- End quote ---
It's not a conclusion, just a guess since he wasn't able to block the address.
I really didn't know why he'd be getting incoming to a container, I wasn't aware that he'd enabled VNC to the NAS.
max096:
--- Quote from: bob on August 04, 2020, 10:43:32 am ---It's not a conclusion, just a guess since he wasn't able to block the address.
I really didn't know why he'd be getting incoming to a container, I wasn't aware that he'd enabled VNC to the NAS.
--- End quote ---
The VNC stuff is all in the container. Since JRiver requires a GUI you kinda sorta have to access it somehow. I dont really want a full blown DE on my servers so that was one of the main reason I even turned to docker for that.
Public accessability and security are always a bit tricky. I would also imagine if bots find a VNC server they would try to tackle it since to me anyways requiering remote desktop on your server would lead me to believe you are an easier target to be hacked. That hacker gonna be pretty disappointed when all he sees is JRiver. ^^
bob:
Great, thanks for the explanation.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version