Actions
Bug #11771
closed
Darkstat WebGUI Cannot be accessed when Pfsense is accessed via a DNS name
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
darkstat
Target version:
-
Start date:
04/01/2021
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
Description
Lets say you have a DNS entry "pfsense-local" the configuration of Darkstat only works when you navigate to 192.168.1.1:666 instead of pfsense-local:666
Since pfsense controls the ports, I thought I should report the issue here.
Updated by Jim Pingle about 4 years ago
- Project changed from pfSense to pfSense Packages
- Category changed from Unknown to darkstat
- Status changed from New to Rejected
- Release Notes deleted (
Default)
There must be something wrong in your testing. The firewall can't tell if it's being accessed by IP address or hostname.
Maybe when you access by hostname it's using IPv6 and darkstat isn't using IPv6 or you don't have IPv6 rules, for example.
But as reported, it's not a valid issue.
Updated by Jon V about 4 years ago
Nevermind, it's the SSL business. The "Access Darkstat" button tries to use SSL and the browser is complaining and not letting the Non-SSL w/DNS name function.
Actions