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

Specifying HTTP/S port in URL reporting 403 error on PFSense 2RC1

Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
1 Posts 1 Posters 2.6k 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.
  • G
    gzartman
    last edited by Apr 4, 2011, 4:52 AM

    I have an install of PFSense 1.2.3 that I've been using for some years at a remote location (Location 1).

    At another location (Location 2), I have both PFsense 1.2.3 and PFsense 2.0RC1.

    If I am at Location 2, connected to PFsense 2.0RC1 and I try to access PFsense 1.2.3 at Location 1 with the url:  https://www.location1.com:8081, I get the browser error:  "The webpage at https://www.location1.com:8081/ might be temporarily down or it may have moved permanently to a new web address."  If I switch my gateway to PFsense 1.2.3, at location 2, at attempt to access PFsense 1.2.3 at location 1, the connect is successful, as it always has been.

    This seems to be a configuration issue with PFSense 2.0RC1, but I can't seem to track it down.

    I am running PFsense 2.0RC1 on a Dynamic IP address provided by Comcast.  My client machine that I'm working from is a Windows 7 notebook.

    Any suggestions would be greatly appreciated.

    Thank you.

    Greg

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