| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 23 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 57:29:45 |
| Calls: | 584 |
| Calls today: | 1 |
| Files: | 1,139 |
| D/L today: |
179 files (27,921K bytes) |
| Messages: | 112,148 |
Using seamonkey, getting
"Unable to communicate securely with peer: requested domain name does
not match the serverrCOs certificate."
Port 563. Port 119 just grinds forever. The e-s support
newsgroup is not carried by mixmin. The e-s status page
shows all green.
Anyone else seeing issues?
maser <invalid@invalid.invalid> wrote:
Using seamonkey, getting
"Unable to communicate securely with peer: requested domain name does
not match the server|ore4raos certificate."
Port 563. Port 119 just grinds forever. The e-s support
newsgroup is not carried by mixmin. The e-s status page
shows all green.
Anyone else seeing issues?
Ray just issued a new checkgroups and there was a mismatch. The problem should be fixed now. Once the solution propogates with an update to control.ctl, ask mixmin to rerun checkgroups and
eternal-september.support should be created. In the meantime, it turns
out that I learned that eternal-september.config is the place to discuss administration of the eternal-september.* hierarchy.
If you need to communicate directly with Ray on these issues, then post
to the eternal-september.* group directly on news.eternal-september.org
which you may do without an account. Ray is unlikely to see the issue
you raise here.
Adam H. Kerman wrote:
maser <invalid@invalid.invalid> wrote:
Using seamonkey, getting
"Unable to communicate securely with peer: requested domain name does
not match the server's certificate."
Port 563. Port 119 just grinds forever. The e-s support
newsgroup is not carried by mixmin. The e-s status page
shows all green.
Anyone else seeing issues?
Thanks for the response.
Ray just issued a new checkgroups and there was a mismatch. The problem >>should be fixed now. Once the solution propogates with an update to >>control.ctl, ask mixmin to rerun checkgroups and
Uh, how do I "ask mixmin to rerun checkgroups" ;)
eternal-september.support should be created. In the meantime, it turns
out that I learned that eternal-september.config is the place to discuss >>administration of the eternal-september.* hierarchy.
If you need to communicate directly with Ray on these issues, then post
to the eternal-september.* group directly on news.eternal-september.org >>which you may do without an account. Ray is unlikely to see the issue
you raise here.
Well, can't post there at the moment nor even read
because of the cert issue.
"Unable to communicate securely with peer: requested domain name does
not match the serverAs certificate."
Port 563. Port 119 just grinds forever. The e-s support
newsgroup is not carried by mixmin. The e-s status page
shows all green.
Anyone else seeing issues?
...---------------------------------------------- "eternal-september" missing(?) >eug.access.video 0000000000 0000000001 y
esp.test 0000000628 0000000625 y
esp.test-moderado 0000000000 0000000001 m
esp.varios 0000000009 0000000010 y
essug.copt 0000000000 0000000001 y
essug.misc 0000000001 0000000001 y
essug.telco 0000000000 0000000001 y
eug.arts.photography 0000000000 0000000001 y
eug.bbs.excelsior 0000000000 0000000001 y
eug.comp.sys.macintosh 0000000000 0000000001 y
eug.config 0000000000 0000000001 y
...
Using seamonkey, getting
"Unable to communicate securely with peer: requested domain name does
not match the serverrCOs certificate."
Port 563. Port 119 just grinds forever. The e-s support
newsgroup is not carried by mixmin. The e-s status page
shows all green.
Anyone else seeing issues?
He switched from SSL to TLS. Does your newsreader support TLS?
He switched from SSL to TLS. Does your newsreader support TLS?
On Tue, 22 Jul 2025 08:51:38 -0400, badgolferman wrote:
He switched from SSL to TLS. Does your newsreader support TLS?
He said it's been like that since 2022. Why is it a problem now?
On Tue, 22 Jul 2025 08:51:38 -0400, badgolferman wrote:
He switched from SSL to TLS. Does your newsreader support TLS?
Well, he ruined it for Agent as well...
<https://i.postimg.cc/255DhQ3V/es-ssl-agent.png>
news.eternal-september.org is working here in Agent, with
'The server requires a secure connection.'
(Agent is configured to allow TLS1.2 or TLS1.3).
(Agent is configured to allow TLS1.2 or TLS1.3).
(Agent is configured to allow TLS1.2 or TLS1.3).
In the E-S newsgroup he said it was done recently. It all worked with
SSL until a week or so ago.
On Tue, 22 Jul 2025 17:55:09 -0400, badgolferman wrote:
In the E-S newsgroup he said it was done recently. It all worked
with SSL until a week or so ago.
I guess you're using W11 as well? Apparently, there was an update
concerning TLS.
On Wed, 23 Jul 2025 11:16:16 +1200, Ralph Fox wrote:
(Agent is configured to allow TLS1.2 or TLS1.3).
Ralph Fox wrote (in eternal-september.*):
<quote>
This (error 80090302) is the error which Agent would give me with E-S,
if Agent did not have the AGENT.INI config change (below) to make it
support TLS1.2 and TLS1.3.
-a *-a Google Groups:-a -a <https://groups.google.com/g/alt.usenet.offline-reader.forte-agent/c/mJmtMSUqp6M>
-a *-a Narkive:-a -a -a -a -a <https://alt.usenet.offline-reader.forte-agent.narkive.com/35h3yv8s/notice-agent-and-ssl>
-a *-a Usenet Archives:-a <https://www.usenetarchives.com/view.php?id=alt.usenet.offline-reader.forte-agent&mid=PHA4aHB1Z2xuYjB0b3Qyb290M29iN204bjFrOTQwa2ZnY2xANGF4LmNvbT4>
-a *-a Message-ID: -a -a -a <news:p8hpuglnb0tot2oot3ob7m8n1k940kfgcl@4ax.com>
</quote>
(Tnx again, Ralph!)
I'm using W11 24H2, so I changed the setting in AGENT.INI to
AllowedSSLProtocols=10880
No more errors for eternal-september.*, but grc.* now results in this
SSL error: 80090308.
On Wed, 7/23/2025 3:01 PM, s|b wrote:
No more errors for eternal-september.*, but grc.* now results in this
SSL error: 80090308.
80090308
"If the component is configured to connect to the remote host in
implicit SSL mode, but the server is expecting explicit SSL,
the SSL handshake will fail with this message."
No luck either way with news.grc.com.
* Connecting to news.grc.com:563 in implicit SSL mode gives error
80090308.
* Connecting to news.grc.com:563 in explicit SSL mode gives an
error from the server, "400 Error initializing TLS".
Their website says [1] they support NON-SSL connections on port 563,
but attempting that gives the error "400 Error initializing TLS".
[1] <https://www.grc.com/discussions.htm>
No luck either way with news.grc.com.
-a *-a Connecting to news.grc.com:563 in implicit SSL mode gives error
-a -a-a 80090308.
-a *-a Connecting to news.grc.com:563 in explicit SSL mode gives an
-a -a-a error from the server, rCL400 Error initializing TLSrCY.
s|b wrote:
On Tue, 22 Jul 2025 17:55:09 -0400, badgolferman wrote:
In the E-S newsgroup he said it was done recently. It all worked
with SSL until a week or so ago.
I guess you're using W11 as well? Apparently, there was an update >concerning TLS.
Xananews is self contained and portable. I run it from a thumb drive.
The SSL .dlls are in its own directory. Unfortunately it seems to be abandoned again. First the author, then the enthusiasts. I can't seem
to find its forum anymore.
In article <105rgfe$13ecq$1@dont-email.me>
"badgolferman" <REMOVETHISbadgolferman@gmail.com> wrote:
s|b wrote:
On Tue, 22 Jul 2025 17:55:09 -0400, badgolferman wrote:worked >>with SSL until a week or so ago.
In the E-S newsgroup he said it was done recently. It all
I guess you're using W11 as well? Apparently, there was an update
concerning TLS.
Xananews is self contained and portable. I run it from a thumb
drive. The SSL .dlls are in its own directory. Unfortunately it
seems to be abandoned again. First the author, then the
enthusiasts. I can't seem to find its forum anymore.
What version are you running?
I sometimes run this. It has limits on what connectivity it will
support.
XanaNews Version 1.21-f3fb89f
Windows 8 (Build 9200)
