- This topic has 35 replies, 4 voices, and was last updated 3 weeks, 2 days ago by
.
-
Posts
-
Yes, I have removed port forwarding for Breakway Remote and I am using TightVNC for remote access. Still no crashes to report since I closed port 8200.
That’s great news. Leif has said that he will look into the code around the port assignment to try and make it more robust.
Just be aware that just about every hacker out there knows the default port address for VNC, so I suggest that you change it from the default and switch it regularly.
Hi again,
Sorry I haven’t reported back for a while.
I have now also removed the port forwarding on 8099 for the internal streaming encoder from my set up and it seems to have cured the restarting.
I am just using external icecast servers for now until this can be resolved.
Something changed somewhere outside of breakaway to cause this issue as it was all working fine for years up until July last year.
Thanks
JohnThanks for the update. Leif is adamant that Breakaway was never intended to be exposed directly to the Internet. However, he is now aware of the issue and will address it in a subsequent release.
I set it up as per one of his videos but perhaps it might be better set up over a VPN rather than directly accessible from the internet?
I’m pretty sure that the video uses VPN, because he advocates that for all end-to-end solutions. It IS possible to set it up using something like dyndns as a forwarding agent, but then you will need port forwarding rules in place and that may start the problem all oer again.
As I have said before, I use Team Viewer security to remotely access the BA1 computer, and then run BARemote locally once I’ve logged in.
- You must be logged in to reply to this topic.