website connection problems with pfsense NAT port forward and DDNS
-
I have this weird connection problem, its even hard to explain in the title.
I am using DDNS to connect to an office location. I have pfsense with some created NAT rules:
port forward port 10000 for virtualmin
This works fine, I can hit the webpage UI and I can login using the credentials.port forward port 80 for webpage
This works, as I can see the webpage itself. However, this website application has an admin login. When I try to login using the admin credentials, it just reloads the page, showing me the login again.What I find strange about this is looking in the /php/sessions/ folder of this app, a bunch of sessions get created, 12 sessions to be specific on that one page login post attempt. A session is stored when visiting this website, every time I hit this website via the DDNS URL it creates exactly 12 sessions. Like its looping.
So, using the DDNS URL I've created, virtualmin works fine, but this custom web APP does not for the /admin/ login via the URL and I can see if creates a bunch of sessions.
If I use the dynamique IP address directly, and log into the /admin/ it works fine. So I'm confused as to where the problem is. Is it DDNS causing me the problem or a misconfigured something in pfsense, or both? Virtualmin on port 10000 does not have a problem with the dyn IP or the URL. Just this APP.
Also, if I'm in the office and use the LAN IP, everything works fine. I did not create a split DNS for internal users to be able to reach this custom APP yet, but I doubt it will be a problem, but didn't check.
And, I we will be moving to a static IP with a true URL in the future. So if its in regard to PTR issues or something that would resolve it. But I'd really like to know what is going on right now...
Any ideas?
Thank you
-
@gstlouis said in website connection problems with pfsense NAT port forward and DDNS:
I did not create a split DNS for internal users to be able to reach this custom APP yet, but I doubt it will be a problem, but didn't check.
So you have no possibility to check this from inside using the host name?
So I would create the DNS entry for testing this with the same conditions. Maybe your app has a problem with the host name. -
@viragomann
I was actually able to test a true .ca domain and it is working. So the APP is having trouble with the DDNS url. I would just like to understand why. There was no errors, PHP warnings or anything at all to give me a lead.I actually edited some code in the APP and only loaded session_start() at the top of the first file php loads for this APP and it still managed to create 2 sessions.
This is clearly not a pfsense problem however
-
@gstlouis Bad cookie? Try a private or different browser.
Could it be trying to redirect to https?