• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Firewall blocking mail server webmail

Scheduled Pinned Locked Moved Firewalling
3 Posts 2 Posters 875 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    skeating
    last edited by Jun 30, 2017, 2:10 PM Jun 30, 2017, 1:20 PM

    Hello

    I have a mail server behind a pfSense firewall. I have port 8100 open to allow access to the SSL cert protected  application. I have pointed the domain name to the mail server in DNS. I should get the WebMail page when I put in, as an example, https://acme.com:8100. Here are my NAT and Rule entries:

    NAT WAN
    WAN TCP      *            *              xxx.xxx.49.33  8100      192.168.31.35  8100

    Rule
    IPv4 TCP      *            *              192.168.31.35  8100          *          none

    Is there something else I need to do, so that the name will resolve to the correct location? When I put in the https:://acme.com:8100, I get "Site cannot be reached ERR_CONNECTION_TIMED_OUT.

    I can connect if I do the https://xxx.xxx.49.33:8100, but it gives me the certificate not safe screen, since the certificate is for acme.com. I have a person on the server who needs things kept simple.

    1 Reply Last reply Reply Quote 0
    • A
      awebster
      last edited by Jul 1, 2017, 7:49 PM

      Based on your explanation, there is a problem with the DNS configuration.
      Make sure that you can resolve the name into the expected IP address first.

      –A.

      1 Reply Last reply Reply Quote 0
      • S
        skeating
        last edited by Jul 1, 2017, 9:38 PM

        Thanks. Did a nslookup from where I was working and realized the DNS return was incorrect. It had not updated since the change. Went to a station outside my network, and the IP was correct.

        Thanks again.

        1 Reply Last reply Reply Quote 0
        3 out of 3
        • First post
          3/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received