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

No port 80, 443 access via openVPN

Scheduled Pinned Locked Moved OpenVPN
3 Posts 2 Posters 946 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.
  • J
    jhuhmann
    last edited by Jan 13, 2015, 2:47 PM

    I have a working openVPN setup on pfsense 2.1.5 and clients can connect without any problems. The problem arises if I try to access any internal or external web service. Any connections on port 80 or 443 fail. If I attempt to access a web service on a non-standard port (8443) it works. I can access internal servers via ssh, rdp, anything I've tried other than a web interface. Initially I thought maybe I was missing some browser configuration or something like that on the client but the same thing happens if I telnet to port 80. The same thing happens if I try to connect to public web servers(ie. google) when connected.

    Has anyone seen anything like this before? I'm open to any suggestions.

    1 Reply Last reply Reply Quote 0
    • J
      johnpoz LAYER 8 Global Moderator
      last edited by Jan 16, 2015, 1:11 PM

      And what are the rules on your openvpn tab in the firewall?  Are you using squid in pfsense as proxy?  Do you have any port forwards setup with those ports?

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

      1 Reply Last reply Reply Quote 0
      • J
        jhuhmann
        last edited by Jan 19, 2015, 3:27 PM

        The only rule I have is the auto generated one, Allow all from all.

        I am not using squid as a proxy. However you asking the question made me start thinking in a different direction. I have a content filter in between pfsense and my network. I bet something is happening there. That would explain why it's just http/https.

        Thanks. If I figure it out I'll update.

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