RSW

Posted: **Mon Jul 22, 2024 4:11 am**

Hello everyone,

I'm new to RSW and I've been unable to get the Mac RSW Client to connect to the RSW server. Any advice would be welcome.

Best regards,

Dave

Error
"Could not connect to RSW. Would you like to switch to offline mode?"
[Yes] [No]

Details
MacOS Sonoma 14.5
RSW Client 1.0.8.6-en-osx
wxPython 4.0.0b2
Python 2.7.10

Configuration
Server: RSW
Comm method: XML connect
[X] Download from this server
Web: http://rswgame.com
Account: xqshnr
Password: •••••••

Wireshark Capture
GET /xml HTTP/1.1
Accept-Encoding: identity
Host: rswgame.com
Connection: close
User-Agent: RSW Client/1.0.8.6-en-osx-gui

HTTP/1.1 302 Found
Date: Mon, 22 Jul 2024 11:45:19 GMT
Server: RSW 1.0.8.7.8 Python/2.7.18
Content-Length: 172
Content-Type: text/html; charset=utf-8
Last-Modified: Mon, 22 Jul 2024 11:45:19 GMT
Cache-Control: no-cache, Max-Age=0
Pragma: no-cache
Expires: Mon, 22 Jul 2024 11:45:19 GMT
Location: https://rswgame.com/xml
Connection: close

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>

</head>
<body>
<a href="https://rswgame.com/xml">Click here</a> to redirect
</body>
</html>

Posted: **Mon Jul 22, 2024 6:21 am**

Update
I've downloaded the Windows RSW Client and it can connect, so I'll try plugging its configuration into the Mac client later today and see what happens.

I think the Mac client picked up goofy defaults that I probably created from the last time I tried to get the Mac client to work (>4 years ago).

Dave

Posted: **Mon Jul 22, 2024 4:51 pm**

Hmm, from everything you posted, I don't see anything wrong; and it seems like the configuration is basically correct since it's able to establish at least the first handshake with the server. That said, I haven't tested the Mac client in more than a few years; and maybe the recent OSX versions introduced some new internet security quirk or something that's blocking the communication?

It could be a port blocking, for instance; the RSW client uses port 80 for the initial communication, but then switches over to port 8123 to exchange xml messages with the server. If something's preventing your Mac from establishing a connection to a remote server on port 8123, that would cause this symptom. Note that it's only an outbound connection, though--no firewalls need to allow connections to your own computer on port 8123 or any other port.

David

Posted: **Mon Jul 22, 2024 4:55 pm**

Ah, you can try changing the Comm method from "XML connect" to "XML web push". That should use port 80 entirely instead of switching over to port 8123. It's a little less efficient, but it's just as capable; and it's less likely to be blocked by any overly sensitive security protocols.

Posted: **Wed Jul 24, 2024 4:13 am**

I've tried a variety of changes to the Mac client, none have worked so far.

Some observations:

When I set the URL to the RSW server to https://, the Mac client uses TLS 1.0, which the server will refuse, and rigthfully so.

When the URL is http://rswgame.com/, the server does a redirect to rswgame.com/xml, but the client doesn't respond to the redirect.

When the URL is http://rswgame.com/xml, the actual URL the client sends is http://rswgame.com/xml/xml, resulting in a 404.

I'm guessing the ancient TLS version, and the not responding to the redirect, are issues within the Python libraries being used by the client. The /xml/xml makes sense from a coding stand point.

--Dave

Posted: **Thu Jul 25, 2024 4:20 pm**

Ah, I think you are right.

Have you tried setting the drop-down to "XML web push" yet? That might mitigate this, the client might be able to do all of its communication via plain HTTP.

David

RSW

RSW Client Not Connecting

RSW Client Not Connecting

Re: RSW Client Not Connecting

Re: RSW Client Not Connecting

Re: RSW Client Not Connecting

Re: RSW Client Not Connecting

Re: RSW Client Not Connecting