Our Nym requester on Victor recently stopped forwarding traffic because
the public Nym gateway it was registered with became unreachable and
refused connections on both its main WebSocket endpoint and fallback IP address.
The gateway was not operated by us or directly by the Nym team. It was a public Nym gateway run by an independent network operator.
The exact reason for the outage remains unknown. Possible causes include
a stopped service, reverse proxy failure, firewall changes, a software incompatibility, or an issue with the operatorrCOs server.
We restored service by registering a working gateway, updating the corresponding requester address on Pietro, and verifying the complete
SMTP and TLS path.
Operating our own Nym gateway is also being considered to reduce
dependence on randomly selected third-party infrastructure.
Gabx wrote:
Our Nym requester on Victor recently stopped forwarding traffic because
the public Nym gateway it was registered with became unreachable and refused connections on both its main WebSocket endpoint and fallback IP address.
The gateway was not operated by us or directly by the Nym team. It was a public Nym gateway run by an independent network operator.
The exact reason for the outage remains unknown. Possible causes include
a stopped service, reverse proxy failure, firewall changes, a software incompatibility, or an issue with the operatorrCOs server.
We restored service by registering a working gateway, updating the corresponding requester address on Pietro, and verifying the complete
SMTP and TLS path.
Operating our own Nym gateway is also being considered to reduce dependence on randomly selected third-party infrastructure.
Hi Gabx,
you should consider using old gateways, which are in service for
already many years, like the ones from wunderbaer, which are
reliable and I use them as well. Or run your own gateway, which
gives you the identity-key for your very own Nym SDK software
components, so that you are the only person responsible for any
outages.
Ch1ffr3punk wrote:
Gabx wrote:
Our Nym requester on Victor recently stopped forwarding traffic because the public Nym gateway it was registered with became unreachable and refused connections on both its main WebSocket endpoint and fallback IP address.
The gateway was not operated by us or directly by the Nym team. It was a public Nym gateway run by an independent network operator.
The exact reason for the outage remains unknown. Possible causes include a stopped service, reverse proxy failure, firewall changes, a software incompatibility, or an issue with the operatorrCOs server.
We restored service by registering a working gateway, updating the corresponding requester address on Pietro, and verifying the complete SMTP and TLS path.
Operating our own Nym gateway is also being considered to reduce dependence on randomly selected third-party infrastructure.
Hi Gabx,
you should consider using old gateways, which are in service for
already many years, like the ones from wunderbaer, which are
reliable and I use them as well. Or run your own gateway, which
gives you the identity-key for your very own Nym SDK software
components, so that you are the only person responsible for any
outages.
P.S. I am currently working on nym-validator CLI, which can
list all exit gateways etc. and can be later included for a
postfix MTA whitelist for a new YAMN remailer network, to
allow only YAMN traffic from Nym exit gateways to remailers
and additionally a remop can set-up a whitelist for outgoing
email addresses too. That way OmniCrap users are excluded,
which spread false informations, insulting people, or sending
death threats etc.
Our Nym requester on Victor recently stopped forwarding traffic becauseOne possibility left out: It could be haunted!
the public Nym gateway it was registered with became unreachable and
refused connections on both its main WebSocket endpoint and fallback IP address.
The gateway was not operated by us or directly by the Nym team. It was a public Nym gateway run by an independent network operator.
The exact reason for the outage remains unknown. Possible causes include
a stopped service, reverse proxy failure, firewall changes, a software incompatibility, or an issue with the operatorrCOs server.
We restored service by registering a working gateway, updating the corresponding requester address on Pietro, and verifying the complete--- Synchronet 3.22a-Linux NewsLink 1.2
SMTP and TLS path.
Operating our own Nym gateway is also being considered to reduce
dependence on randomly selected third-party infrastructure.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 74 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 30:16:00 |
| Calls: | 1,195 |
| Files: | 1,354 |
| D/L today: |
16 files (19,622K bytes) |
| Messages: | 294,275 |