According to the vendor of the Chromium component, it is related to a feature/protocol used by the web server which isn't supported by the proxy server. When using a secure gateway, a very basic local SOCKS proxy is started on the client machine to utilize the SSH based local port forwarding tunnel. There's a good chance that the target web server is using more advanced protocols without any fallbacks which may cause issues like this. Can you provide more information what kind of web server/web app you are trying to connect to? If we can reproduce the issue, we could look into it.
We are currently experiencing the same issue when trying to connect to our Synology devices (Disk Stations and Rack Stations, running DSM 7) via a royal server secure gateway.
Is there a possibility to get this issue fixed? How can we help you with finding a solution?
Are you running the latest version of Royal TS? If so and you still experience issues, can you try the following:
- Open the web page connection
- Use the Active Tunnels panel to find out on which port the SOCKS proxy is listening
- Configure the standard Chrome browser to use localhost/127.0.0.1 with the port shown in Royal TS as a SOCKS proxy
- Try to connect to your web server using the same URL in the standard Chrome browser
Regards,
Stefan
Thank you for you quick response. We running the lastest version of Royal TS and Royal Server.
I'm struggling a bit with following your instructions, sorry. I found the active connection (see attached file), but I don't really understand how to continue. Could you explain in a bit more detail, how to do steps 2 and 3? Like, do you mean the Chrome browser on my client or in Royal TS? I'm a bit confused, sorry ;-)
I'm sorry for the confusion. Let me explain what the secure gateway for web connection is doing in more detail:
A secure gateway connection is basically setting up a local port forwarding tunnel. This means that on your machine (where Royal TS runs) a dynamically assigned local port on 127.0.0.1 will have a listener running which forwards every communication to the target host "behind" the secure gateway.
For web pages, the concept is the same, except that on the dynamically assigned local port a SOCKS proxy is started and forwards all web page traffic to the secure gateway which in turn communicates with the target host(s). In this sense, the secure gateway acts as a SOCKS proxy server which is accessible through the dynamically assigned local port (which you can see in the Tunnels panel).
So when you open this web page connection, the local host and port from your screenshot would be 127.0.0.1:51133. This means that on this IP/port a socks proxy is running (as long as the connection/tunnel is open).
You can go to Chrome (which opens the System Settings) and configure this in the proxy settings. So as long as the tunnel is working, Chrome would be using the very same proxy server from Royal TS as your connection.
The way the Chromium engine in Royal TS works is slightly different but it would be interesting to know if the issue is only present in the Chromium of Royal TS or the Chrome browser as well.
I hope this makes sense.
Regards,
Stefan
Sergio Guijarro
After configuring a website through Secure Gateway, I received an error code without any description:
Load failed: "Error code:-336"
Gravedad: Warning
CategorÃa: WebPage.Chrome
What concerns to that code?
I can open in Royal Server the website with the local browser without problems.
1 person has this problem