Remote Admin Connection Problem | MDaemon Technologies, Ltd.
  1. Forum
  2. MDaemon
  3. Remote Admin Connection Problem

Remote Admin Connection Problem

  • J

    MDaemon 23.5 on Server 2022

    I use a redirect to access remote admin, webadmin.domain.com which translates to mail.domain.com:444.  Yesterday remote admin stopped working on the LAN and from outside the router.  Remote adimin ports 444 and 1001 are listening on the server and I can access on the server itself via Chrome using webadmin.domain.com so the redirect is working properly.  However, from any computer on the LAN I cannot connect.  Here is a snippet from the WDaemon log:

    Sun 2023-12-10 16:17:16.729: [389] Winsock accept error: 0.
    Sun 2023-12-10 16:17:16.745: [390] Winsock accept error: 0.
    Sun 2023-12-10 16:17:16.791: [391] Winsock accept error: -2146893007.
    Sun 2023-12-10 16:17:16.883: [392] Winsock accept error: 0.
    Sun 2023-12-10 16:17:16.885: [393] Winsock accept error: 0.
    Sun 2023-12-10 16:17:16.948: [394] Winsock accept error: -2146893007.
    Sun 2023-12-10 16:17:16.956: [395] Winsock accept error: -2146893007.
    Sun 2023-12-10 16:22:13.563: [399] Winsock accept error: 10054.
    Sun 2023-12-10 17:42:31.491: [416] Winsock accept error: 0.
    Sun 2023-12-10 18:04:05.001: [479] Winsock accept error: 0.
    Sun 2023-12-10 18:07:38.241: [507] Winsock accept error: -2146893017.
    Sun 2023-12-10 18:07:40.378: [509] Winsock accept error: 10054.
    Sun 2023-12-10 18:07:40.767: [510] Winsock accept error: 0.
    Sun 2023-12-10 18:07:41.970: [511] Winsock accept error: 10054.
    Sun 2023-12-10 18:07:42.436: [512] Winsock accept error: 10054.
    Sun 2023-12-10 18:07:42.964: [513] Winsock accept error: 0.
    Sun 2023-12-10 18:07:44.136: [514] Winsock accept error: 10054.
    Sun 2023-12-10 18:07:44.332: [515] Winsock accept error: -2146893048.
    Sun 2023-12-10 18:07:44.739: [516] Winsock accept error: -2146893048.
    Sun 2023-12-10 18:07:45.243: [517] Winsock accept error: -2146893007.
    Sun 2023-12-10 18:07:45.679: [518] Winsock accept error: -2146893048.
    Sun 2023-12-10 18:14:32.802: [535] Winsock accept error: 0.
    Sun 2023-12-10 18:14:33.160: [536] Winsock accept error: 0.
    Sun 2023-12-10 18:14:33.509: [537] Winsock accept error: 0.
    Sun 2023-12-10 18:14:33.875: [538] Winsock accept error: 0.
    Sun 2023-12-10 18:14:34.232: [539] Winsock accept error: 0.
    Sun 2023-12-10 18:14:34.596: [540] Winsock accept error: 0.
    Sun 2023-12-10 18:14:34.771: [541] Winsock accept error: -2146893048.
    Sun 2023-12-10 18:14:35.312: [542] Winsock accept error: 0.
    Sun 2023-12-10 18:14:35.499: [543] Winsock accept error: -2146893007.
    Sun 2023-12-10 18:14:36.036: [544] Winsock accept error: 0.
    Sun 2023-12-10 18:14:36.220: [545] Winsock accept error: -2146893048.

    Any thoughts as to why this is happening?

    Thanks,

    Jay

    0 likes
  • A

    What are you using to do the redirecting?  Is that device logging any errors?  

    When on the LAN, are you typically allowed to access https://mail.domain.com:444 or http://mail.domain.com:1001?  Is it currenlty working?

    If you run fiddler on one of the LAN machines and try to access http://webadmin.domain.com what does it show is happening?

    For the HTTPS connections, can you confirm the certificates are still valid and that they support the host names you are connecting to?

    --
    Arron Caruth

    0 likes
  • J

    I use Oracle Cloud Infrastructure for DNS and Redirection.  Redirection is working for webmail.domain.com which redirects to https://mail.domain.com:443 , but webadmin.domain.com is not working.  Even if I enter the redirection address manually, https://mail.domain.com:444 it does not work.  I am not familiar with Fiddler but I will give it a try.  As for certificates, Let's encrypt renewed the certificate just before this occurred, however, email accounts are working in Outlook as is Webmail.

    0 likes
  • J

    @Arron

    [Fiddler] The connection to 'mail.domain.com' failed. <br />Error: TimedOut (0x274c). <br />System.Net.Internals.SocketExceptionFactory+ExtendedSocketException A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 173.x.x.x:444
    0 likes
  • J

    @Arron I restored an image from two weeks ago just before the certificate update and re-ran Let's Encrypt update and now Webadmin works.  Something must have gone wrong when I ran the Let's Encrypt update the first time.  Thank you Arron for your time and the question that triggered the solution to the problem.

     

    0 likes
  • A

    I'm glad you got it working again.  

    --
    Arron Caruth

    0 likes
Please login to reply this topic!