Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
same issue: https://github.com/ValveSoftware/steam-for-linux/issues/6605
This has to be client related.
I tried copy-pasting this one on my regular browser (brave/chromium) and it retrieved the image without a problem. Maybe there is a problem with the steam client implementation itself and not with the curl libs.
P.S: I also tried using the curl command itself from the command-line interface and it downloaded the picture as well. Further indicating that this is indeed a problem with the steam client itself.
the reference reads like this if you open it as an html file on the browser:
P. S: Maybe steam uses its own local version of libcurl instead of the global libraries installed in my linux machine?
THE REMOTE PLAY WORKS FINE ON THE LOCAL NETWORK.
What i have noticed after testing is that, while the remote play client does try to connect to the right ip address in a physical local network:
It tries to connect to the 0.0.0.0 ip address, at port 0, which is not a valid address, whenever you try to connect from an external network. Note that this is not a firewall issue, as the steamlink android app still work anyways in the same conditions, and the error still reproduces when using a VPN
The steam client can launch a remote play session in two different modes: LAN and online.
On LAN mode, it connects directly to the home device using its local ip address.
On online mode, steam gets your public ip from the two computers you have logged in from, and then connects to the steam servers to establish an internet connection between the two. In doing so, the connection to the steam servers fail for whatever reason, and the remote session crashes.
The problem is that steam, for some reason, prioritizes the online mode over LAN when connected through VPN/hamachi, rendering them useless. Otherwise we could use that to bypass online mode and establish a direct connection between both devices.
Is there a way we can "force" remote play into LAN mode? Or at least prioritize the vpn connection?