<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Specifying HTTP&#x2F;S port in URL reporting 403 error on PFSense 2RC1]]></title><description><![CDATA[<p dir="auto">I have an install of PFSense 1.2.3 that I've been using for some years at a remote location (Location 1).</p>
<p dir="auto">At another location (Location 2), I have both PFsense 1.2.3 and PFsense 2.0RC1.</p>
<p dir="auto">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.</p>
<p dir="auto">This seems to be a configuration issue with PFSense 2.0RC1, but I can't seem to track it down.</p>
<p dir="auto">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.</p>
<p dir="auto">Any suggestions would be greatly appreciated.</p>
<p dir="auto">Thank you.</p>
<p dir="auto">Greg</p>
]]></description><link>https://forum.netgate.com/topic/32355/specifying-http-s-port-in-url-reporting-403-error-on-pfsense-2rc1</link><generator>RSS for Node</generator><lastBuildDate>Mon, 20 Apr 2026 12:38:34 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/32355.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 04 Apr 2011 04:52:27 GMT</pubDate><ttl>60</ttl></channel></rss>