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

WebGui inaccessible from LAN after OpenVPN server enabled…Huh??

Scheduled Pinned Locked Moved General pfSense Questions
25 Posts 2 Posters 3.4k 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.
  • D
    Derelict LAYER 8 Netgate
    last edited by Apr 24, 2015, 3:56 PM

    Where are you accessing the webgui from?  What address are you accessing?  You are also not getting the route(s) for the remote networks so that's still buggered.  You should probably post your serverX.conf from /var/etc/openvpn.

    Chattanooga, Tennessee, USA
    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
    Do Not Chat For Help! NO_WAN_EGRESS(TM)

    1 Reply Last reply Reply Quote 0
    • J
      JimPhreak
      last edited by Apr 24, 2015, 4:14 PM Apr 24, 2015, 4:03 PM

      @Derelict:

      Where are you accessing the webgui from?  What address are you accessing?  You are also not getting the route(s) for the remote networks so that's still buggered.  You should probably post your serverX.conf from /var/etc/openvpn.

      I'm accessing from a PC on my LAN (192.168.4.50).  I'm trying to access https://192.168.4.1 like I always do from the LAN.  Right now I have no remote networks configured in the OpenVPN server.  I tried to strip it down as much as possible to isolate the problem.  So the only network configured in the OpenVPN server is the VPN network itself (10.0.8.0/32) which is why the remote networks are not showing up.

      How can I view that config file from the console?  I can get into the directory fine but not sure how to view/access the file.  Sorry not very familiar with FreeBSD commands.

      Just not computing for me that I can access the server fine over SSH from my PC but not via HTTPS.  How can that be a routing issue?

      1 Reply Last reply Reply Quote 0
      • J
        JimPhreak
        last edited by Apr 24, 2015, 4:47 PM

        Found the issue.  Turns out it is a bug.  Not so much with pfSense itself but with the bandwidthd package.  Once uninstalled I'm all good now.

        1 Reply Last reply Reply Quote 0
        • D
          Derelict LAYER 8 Netgate
          last edited by Apr 24, 2015, 4:54 PM

          Damn packages.  Don't know why people install them.  No wonder pfSense "just works" for me and not for other people.

          Glad you found it.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • J
            JimPhreak
            last edited by Apr 24, 2015, 4:55 PM

            @Derelict:

            Damn packages.  Don't know why people install them.  No wonder pfSense "just works" for me and not for other people.

            Glad you found it.

            I don't really use them either, I might as well uninstall most (if not all) of them.

            Thanks for the continued back and forth dialogue though.  Much appreciated.

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