Help forwarding to webdav share
-
Gotcha. So you have a web server running over at dyn that listens and when it gets a hit on HTTP if simply sends a redirect to that URL.
Why not make the redirect go to http://myddnsname/webdavshare and update that hostname with ddns?
-
I don't think I follow what you mean…So have it redirect to http://webdav.ddns.net:5385/webdavshare/ I don't think that would work, or am I misunderstanding you?
-
No. Create another dyndns hostname. Update that hostname with ddns based on pfSense WAN. Have the redirect URL point to that.
-
It needs to point to the webdav share though. Pointing just to to the port won't get to it.
-
Dude. You will still have the web redirect. It will just point to a second ddns name instead of an IP address.
-
I understand what you're saying, but the 2nd ddns name would still need to be configured to point to an ip address. In my case a dynamic one.
So webdav.ddns.net redirects to webdavshare.ddns.net which redirects to the share on 86.128.xx.xx:5385/webdavshare/
Whilst Webdav.ddns.net would keep up to date with any IP changes I'd still need to change the actual share name manually. I think the onlky way around this is to get a static IP but my ISP don't offer them.
-
Ok. One more time. Look at the screenshots below.
 -
It doesn't allow you to do that though, it comes back as being an invalid url address.
-
What's IT? This certainly has absolutely nothing to do with pfSense. What's this redirect nonsense? Register some DDNS host and get it updated via pfSense. Type the URL into your WebDAV client instead of doing some whacky absolutely useless "redirects" using god knows what service.
-
Yeah, with two colons before the port number it's going to complain it's an invalid URL.
-
Two colons or not
- these "DNS" records do NOT point to your dynamic IP (see below)
- these records do NOT work properly with tons of WebDAV clients since the redirect is done via a webserver of the DynDNS provider (better case would be via webserver's configuration, but it can be done via PHP, HTML or even JS or - yuck - frames)
::) :o
-
What's IT? This certainly has absolutely nothing to do with pfSense. What's this redirect nonsense? Register some DDNS host and get it updated via pfSense. Type the URL into your WebDAV client instead of doing some whacky absolutely useless "redirects" using god knows what service.
It's no-ip DDNS service that I'm using. And Ideally I need this accessible via a web browser rather having to have some 3rd party client software installed. I need customers to be able to access it and download files, I could do without having to ask them to install software beforehand, much easy to send them a link to the share.
-
So send them the link? Really no idea what are you trying to do with the redirect URLs. It won't work properly or at all.
-
The problem I've got is that my ISP uses dynamic IP addresses and it changes a couple of times of week. Therefore sending out a link to the share will only work until my public IP changes. By doing the redirect and pointing to a DDNS name rather than an IP would have solved this problem.
-
Uh. Yes. Replace your dynamic IP in the link with the dynamic hostname. Do NOT use any URL-redirect type service for this. It will NOT work properly and is absolutely NOT needed. In the screenshot above, you should use DNS host (A), and NOT URL!
(And as already noted above, behind double NAT, port-forwarding on pfSense alone will do zilch and it still will not work. Get rid of the double NAT or forward this in both places.)
-
OMFG I surrender.
-
Uh. Yes. Replace your dynamic IP in the link with the dynamic hostname. Do NOT use any URL-redirect type service for this. It will NOT work properly and is absolutely NOT needed. In the screenshot above, you should use DNS host (A), and NOT URL!
(And as already noted above, behind double NAT, port-forwarding on pfSense alone will do zilch and it still will not work. Get rid of the double NAT or forward this in both places.)
The reason I tried this whole web redirect was because what you're suggesting doesn't work. That's exactly how I had it configured to start with.
So…..http://webdav.ddns.net:5385:/webdavshare doesn't work.
And I'm not double Nating, everything is off on the modem, it's in bridge mode to my pfsense box.
-
Yes. Because when your pfSense WAN IP is RFC1918 (192.168.1.16) then it won't work as noted above, multiple times. Go do some reading on double-NAT and bridging modems. You are messing with totally wrong stuff here.
-
webdav.ddns.net is setup with my public IP, I'm not double Nating. Everything is switched off on my modem and it's in bridge mode PPPoe with my pfsense box.
-
And I'm not double Nating, everything is off on the modem, it's in bridge mode to my pfsense box.
You know, grab some WebDAV client that provides some logging and debugging output (no, Windows Explorer is NOT one) and produce some info here when testing from your WAN. And for the last time, the URL forwarding is complete BS. Also, the WebDAV server should have logs.
