Welp, still seems that I'm failing at getting the launcher (or proton?) to respect the proxy in some way. It doesn't even try to update horizons because it relies on steam for that. Then tried again after changing VersionInfo.txt for Horizons and starting the horizons launcher. With the prefix set up, set launch options to http_proxy=127.0.0.1:9200 %command% and selected default launcher to update the alpha not seeing any https again, nor requests to the API. (think that's because actually requires Proton 5.13 and above?) Removed the existing prefix, launched it to create a new one, protontricks 359320 -q dotnet472 win7 because for some reason wine-mono makes my launcher crash on pressing play/upgrade. So steps taken with mitmproxy certificates trusted systemwide (moved to /usr/local/share/ca-certificates/mitmproxy.crt and imported with sudo update-ca-certificates) and forced proton 5.0-10: I don't know if wine/proton has its own certificate storage, would explain this if it actually does.Ĭurrently trying to plug all http/s traffic through this, but simply redirecting ports 80 and 443 to 9200 yields 502 Bad Gateway pretty much everywhere, and setting a proper systemwide proxy is unfortunately not trivial with just bare NetworkManager, from what I can tellĪll of the above was indeed performed with proton 5.0-10 because for some reason I couldn't get the stock launcher to work at all now on 5.9-GE or any pressure-vessel-using versions, with neither wine-mono_ED nor dotnet472. However, launching Elite from steam with http_proxy=127.0.0.1:9200 https_proxy=127.0.0.1:9200 %command% still yields the same results as before with only one or two weird image requests through https from the launcher and nothing at all during the upgrade, but this time the launcher also complained about certificate issues, no change after selecting "Yes" when asked to proceed anyway. Made sure to correctly install the certificate systemwide this time, was able to successfully look at https traffic from the browser with a configured proxying, or anything launched with http_proxy=127.0.0.1:9200 https_proxy=127.0.0.1:9200.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |