Search results

v1.27.1 is now available: - Further fixes for clipboard sharing on PC host/client - Fixed PC client UI not displaying properly on non-standard desktop scaling (like 115% etc.)

Hi vamp, we have just expanded our team. This will allow us to speed up v2.0 development. The roadmap for v2.0 includes: 1. iOS client (port form Android, Q1 2025) 2. macOS client (iOS client should work on M1/2/3/4 CPU macOS devices) 3. WebRTC client (already in the works, should be ready ~Q1...

Hi Everyone, Below please find the change log for this update: - Fixed clipboard sharing enable/disable option (clipboard sharing can now be enabled/disabled during connection using Settings->Security option) Please note that after disabling clipboard sharing, CTRL+C will not work for both...

Great. Can you check (on both routers) are there any port-forwarding rules already present? In Remotly Settings->General there is an option (you may need to scroll down): "Use custom P2P port numbers" You can enable this option and a window will show where you can set Inbound/Outbound ports...

"They suggest me just reboot my router" = don't bother us :) Typical. We had a situation once in our labs when P2P worked great for LTE and suddenly it stopped working. After deeper analysis we found out ISP has changed hardware in the BTS... Later it started working again. As for torrent it...

It may not be a problem with host PC but even with the connecting Remotly client. P2P might be blocked by the ISP that allows internet access by your client when you are abroad.

Hi Wander. Are you able to login to your main (border) router? Do you have more than one router?

Hi Everyone, Below please find the most important changes in this update: - Intelligent selection of GPU used for encoding depending on video source (minimizes data transfers between GPUs) - Improvements for 120Hz, 144Hz and 240Hz displays - Improved 120fps streaming (PC Client) - Fixed...

Your account's admin panel... There is no Linux server panel admin/config (yet).

https://remotly.com/login

It's OK. You will get this message after entering public_ip:443 without any parameters. But it will work after setting it in your admin panel and then using your private server for connections.

Next add the custom relay in your admin panel (public IP and 443 as port). Please do not post your public IP on the forum 😉

It works :) everything is ok. Now you must port forward port 443 to this local IP (192.168.1.215 in this case) in router settings to make it public and accessible from external networks.

https://community.remotly.com/threads/remotly-private-relay-server-for-linux-arm-devices-is-now-available.180/#post-993

You can now create you own private relay server on ARM devices like Raspberry Pi. A detailed step-by-step tutorial below: 1. First, we need to access the remote machine's Linux system using SSH client. To establish SSH connection, client will ask to provide host IP address and user...

We are preparing a separate zip. It will be available tomorrow with user manual (please check on the forum under Linux support tomorrow).

Hola Drakener, La compatibilidad con la presión y la inclinación del lápiz óptico estará disponible a finales de este mes.

Please check tomorrow evening :) We are already testing the Raspberry ARM version.

There is a major bug when P2P with error correction is enabled in General Settings. Sometimes control is lost and Remotly app for Android must be restarted to recover from this state. PLEASE DISABLE P2P WITH ERROR CORRECTION IN GENERAL SETTINGS until a fix is ready.

Current version will not work on ARM. We will upload a Raspberry dedicated version next week with installation manual.