Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. SFTPGo
  3. How to disable the webdav protocol?

How to disable the webdav protocol?

Scheduled Pinned Locked Moved SFTPGo
5 Posts 3 Posters 48 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    ctrl
    wrote last edited by ctrl
    #1

    Hey all,

    is there a way to disable the webdav protocol entirely?
    According to the official docs setting the listening port to 0 implies the service is disabled. But manually setting the default port in /app/data/sftpgo.json 8888 to 0 does not work as its value gets overwritten upon a restart of SFTPGo. Is this a bug maybe? The Cloudron docs propose to put custom settings in said json file. On a sidenote this does also not allow to set the connection to use HTTPS.
    However it would be nice anyway to be able to configure the protocol inside the app location section where we are able to toggle SFTP and FTP.

    1 Reply Last reply
    1
    • jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by
      #2

      Hello @ctrl
      The webdav port can not be changed and is configured by the app itself on each startup.
      For webdav there is the second domain for the app, by default sftpgo-webdav.DOMAIN.TLD, which you should you for https webdav connections.

      C 1 Reply Last reply
      1
      • jamesJ james

        Hello @ctrl
        The webdav port can not be changed and is configured by the app itself on each startup.
        For webdav there is the second domain for the app, by default sftpgo-webdav.DOMAIN.TLD, which you should you for https webdav connections.

        C Offline
        C Offline
        ctrl
        wrote last edited by ctrl
        #3

        @james said in How to disable the webdav protocol?:

        The webdav port can not be changed and is configured by the app itself on each startup.

        Well yes, that is my whole point. ^^
        The question is why it is set up like this because according to the SFTPgo docs it does not seem to be enabled by default.

        The WebDAV support can be enabled by configuring one or more bindings inside the webdavd configuration section.

        I'm looking for a way to disable it constantly because it is not needed in many use cases/scenarios.
        Also in cases where it is enabled it should use https instead of http, doesn't it?

        1 Reply Last reply
        1
        • jamesJ Offline
          jamesJ Offline
          james
          Staff
          wrote last edited by
          #4

          Hello @ctrl
          WebDAV is enabled by default for the Cloudron app version of SFTPGo, it will always be the default port 8888 internally which will bet set each time on app startup.
          But, port 8888 is never publicly exposed, so you can only connect via https on the secondary domain.
          Unfortunately, it is currently not possible to have secondary domains optional for Cloudron apps.
          So either the feature exists or it does not.
          In the case of the SFTPGo app this means choosing to offer WebDAV support or to not offer WebDAV support.
          We opted to offer the WebDAV support.

          1 Reply Last reply
          1
          • J Online
            J Online
            joseph
            Staff
            wrote last edited by
            #5

            To add to what @james said, any secondary domains in httpPorts is non-optional. I guess you can raise this as a feature request to have optional httpPorts (just like tcpPorts and udpPorts can be optional and disabled at run time).

            1 Reply Last reply
            1
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Bookmarks
            • Search