Topic: webdav over https

[emissions]

a client pc on the local is attempting to map a webdav over https which is failing.

mapping to the same webdav on home network does not have any issues.

sme server latest update of 9.2
mode:  servergateway with email
security settings are all default.

would this be blocked by the firewall "out of the box" so to speak?

how do I open this?

thank you for the help.

[emissions]

I should clarify that the webdav share is not on the sme box .. the box is simply serving as the local network gateway the client pc is on.

the webdav share is external.

client pc firewall / virus settings have been ruled out.

[emissions]

Would the mod_dav contrib effect this?

Code: [Select]

yum install smeserver-mod_dav --enablerepo=smecontribs
Seems more like a firewall / proxy issue to me but the mod_dav contrib is basically what I'm after only in reverse without interaction of our server ibays.

[Jean-Philippe Pialasse]

mod dav is for creating a dav on the sme.

If I understand you search to do this :

client  <====== INTERNET =======> SME SERVER <====LAN===> PC1 with DAV in https

I assume you have a valide certificate on the PC1

What you are searching  is either a port redirection or a reverse proxy.
1- for proxy the difficulties will be :
- we do not know if you want to redirect a whole domain or a single folder. However here is the doc for both : https://wiki.contribs.org/SME_Server:Documentation:ProxyPass
- the biggest issue will be the https, if As I understand you already have a valide https cert on the PC1. You will need to be able to have the exact same cert on the SME to enable full https connection without alert for man in the middle attack. Having only the SME connection with https would be easier, leaving the proxypass connection between SME and PC1 in clear over the lan.

2- port redirection, as you already use 80 and 443 ports you will need to decide to use a non conventional port let's say : 43443 and go to the server manager to configure the port redirection from 43443 on wan, to 443 on lan toward PC1 ip. see https://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter11#Port_forwarding
 

solution

[emissions]

Thank you for the reply Jean-Philippe

The flow would be as follows....

client  <====== LAN =======>XX SME SERVER <====INTERNET===> PC1 with DAV in https (HAS VALID CERT)

XX = Appears to be where to be the point of failure to connect.

Removing SME Server from the path by connecting directly through the ISP works.

[Jean-Philippe Pialasse]

Thank you for the reply Jean-Philippe

The flow would be as follows....

client  <====== LAN =======>XX SME SERVER <====INTERNET===> PC1 with DAV in https (HAS VALID CERT)

this way should works straight forward and I access few webdav this way.

XX = Appears to be where to be the point of failure to connect.

Removing SME Server from the path by connecting directly through the ISP works.

Do you mean connecting your PC directly in place of the SME ? Or through another connection from same ISP , other ISP ? From reading agin your first comment I understand from another connection, maybe different ISP.

without all  information we can not help you.

First thing is what does it means "is failing." What is the expected result what do you get ? what is the error ?, HAve you search the log on your PC, on the remote server ? on the SME ?

So what it could be, and without limitation to only this list :
- your ISP blocking this server
- your ISP having issue routing to the remote server
- your LAN subnet is not ad hoc and conflict with an internet subnet used in the routing between you and the webdav server.
- you SME is not directly connected to internet but the modem is acting also as router and has some firewall enabled.
- you installed a software or a contrib that prevent outgoing connection
- you altered in an unknown way you SME
...
- a bug