httpS WebDAV shares not accessible, http access is OK

[mudshark]

Unencrypted webDAV share is fully accessible, can successfully map a drive over the internet.
==> Used format locally as: http://192.168.1.171:8080/Sharename
WebDAV settings:
* http only
* Port 8080
* Basic Auth
* UserID is webdav

Change to an HTTPS connection,
==> Used format locally as: https://192.168.1.171:8081/Sharename
==> "An unexpected network error occurred."

I created a new internal CA using default settings where they exist
I created a new internal certificate using default settings where they exist
I open the WebDAV service config and set options thusly:
* https only
* Port 8081
* Digest Auth
* UserID is webdav

Now I can no longer map that share, I rec'v the error above.

If I'm not mistaken, this was working properly until I installed the FreeNAS system update to ver:
FreeNAS-9.3-STABLE-201503270027

If this is a known issue w/ the latest FreeNAS update I'll roll back (Does anyone know how to do that?)

Otherwise, how do I find why the encryption is failing?

Thanks all!
RG

 

[rogerh]

If this is a known issue w/ the latest FreeNAS update I'll roll back (Does anyone know how to do that?)

Thanks all!
RG

It may be related to https://bugs.freenas.org/issues/8828

If so, you need to wait for the next update or revert back to before 20150320. Or possibly just choose HTTP+HTTPS in the GUI for Webdav instead of HTTPS - but I have no idea if this actually enables you to use https. If it does, this may be a quick solution. The bug report implies it might.

To roll back: in the GUI, go to "System" on the top line, then the "Boot" tab and click on the boot image before 20150320. I have got two boot images with that date for odd reasons, so make sure you go back to at least 20150317. The bottom one will be marked "On Reboot, Now". Having selected the relevant one, press the "Activate" button and wait an extraordinarily long time until "On Reboot" appears on the selected line. (The bottom line will still be marked "Now" for obvious reasons.)

Then reboot and you will have rolled back to the chosen update. I can't guarantee Webdav was working in 20150317, but the bug report implies it!

 

[rogerh]

Did you solve your problem?

 

[mudshark]

My solution for now is NOT to use WebDAV as I do not want to put unencrypted logins out there.
Not what I wanted but...

 

[rogerh]

My solution for now is NOT to use WebDAV as I do not want to put unencrypted logins out there.
Not what I wanted but...

Well apparently the solution (if it applies to your problem) will be in the next update to come out.

 

[mudshark]

Thx! We hope this is the answer...

 

[mudshark]

My FreeNAS build is currently up-to-date, at FreeNAS-9.3-STABLE-201506162331.

==> I still *cannot* establish a secure (https) connection to my WebDAV share.

I can connect with an http connection with "Digest Authentication" but what good is that if it sends the password in clear text, right? (So, BTW, what good is Digest Authentication w/o https?)

The WebDAV service is configured for http + https
Port forwarding is correct.
Basic v digest authentication makes no difference.
No trouble with the http connection.
Windows error is: "Network name cannot be found"
http: works as: http://myvaliddomain.net:nnn/WebDAV
https fails as: https://myvaliddomain.net:xxx/WebDAV
where nnn=http webdav port + xxx=https webdav port

Where to start looking?

Thanks all.
Rich

 

[Sc0rc3d]

My bad, now it works