[Bug] Walrus Memory Testnet staging endpoints return mismatched TLS certificates #1298

Surface

Relayer / hosted API

Network

Staging (relayer-staging.memory.walrus.xyz)

Package version

Not applicable — reproduced with curl before SDK initialization

What happened?

Hi Walrus Memory team,

I'm building Walguardian (https://walguardian.vercel.app/), an AI-powered financial copilot on Sui that uses Walrus Memory to retain financial preferences and past decisions.

While integrating Walrus Memory on Testnet, I encountered a TLS certificate hostname mismatch on the staging relayer.

The endpoint https://relayer-staging.memory.walrus.xyz resolves successfully and accepts TCP/TLS connections, but presents a certificate for *.up.railway.app rather than relayer-staging.memory.walrus.xyz.

As a result, HTTPS certificate verification fails and the application cannot establish a secure connection to the Testnet relayer.

The staging dashboard (https://staging.memory.walrus.xyz) has also shown certificate or availability problems during our integration checks.

Could you confirm whether these Testnet endpoints are still supported and whether updated staging endpoints are available?

Steps to reproduce

1. Open a terminal on macOS.
2. Run:

curl -Iv https://relayer-staging.memory.walrus.xyz

3. Observe that the hostname resolves and the TLS handshake proceeds, but certificate hostname validation fails.

This was reproduced independently on a MacBook on October 25, 2026. The same certificate mismatch was also observed during our development environment checks.

Expected

The Testnet staging relayer should present a trusted TLS certificate whose Subject Alternative Names include relayer-staging.memory.walrus.xyz.

Developers should be able to connect to the documented Testnet endpoint with normal HTTPS certificate verification enabled.

Actual

The server presents a TLS certificate with CN=*.up.railway.app, which does not match the requested hostname relayer-staging.memory.walrus.xyz.

The client terminates the HTTPS request with curl error 60. The Walrus Memory Testnet relayer is therefore inaccessible through normal TLS verification.

Logs or error text

* Host relayer-staging.memory.walrus.xyz:443 was resolved.
* IPv4: 69.46.46.112
* Connected to relayer-staging.memory.walrus.xyz (69.46.46.112) port 443
* SSL connection using TLSv1.3
* Server certificate:
*  subject: CN=*.up.railway.app
*  start date: Sep 27 03:01:43 2026 GMT
*  expire date: Dec 26 03:01:42 2026 GMT
*  subjectAltName does not match host name relayer-staging.memory.walrus.xyz
* SSL: no alternative certificate subject name matches target host name 'relayer-staging.memory.walrus.xyz'
curl: (60) SSL: no alternative certificate subject name matches target host name 'relayer-staging.memory.walrus.xyz'


Environment:
- OS: macOS
- Client: curl / OpenSSL TLS validation
- Endpoint: Walrus Memory Testnet staging relayer
- Date: October 25, 2026

No credentials, private keys, or authentication tokens are included.

Checks

• I searched existing issues and this is not a duplicate.
• This report contains no private keys, mnemonics, or other secrets.