Owncloud Webdav Error 405
Contents |
of Life) ownCloud Community Edition 6.x Search Client: 405 Method not Allowed Ask all your questions regarding OC 6.x Please read the Support Forum Rules Forum rules ownCloud 6.x reached apache webdav 405 method not allowed end of life and is officially unsupported. For details see Wiki page.Please upgrade
Webdav Propfind 405
your ownCloud. Locked Print view Search Advanced search 9 posts • Page 1 of 1 marcel504 Newbie Posts: 7 Joined: http 405 method not allowed Tue Nov 26, 2013 12:32 pm Webserver: IIS Database: MySQL OS: Windows Server PHP version: 5.3.X Client: 405 Method not Allowed Quote Postby marcel504 » Tue Nov 26, 2013 12:40 pm Hello people,i nginx webdav have the problem that my desktop clietn cant connecet to my ownCloud server. I can access he server through my website and i can accees the webdav folder on my website. Im running the 6.0.0 beta cause the versioon 5 caused way too many problems with my server.One thing i think is strange is that if i type https://owncloud.marxxxx.xx/ into the connection assistant i cant connect
Linux Webdav Server
and when i type http://owncloud.marxxxx.xx/ it connects and ask me for an user name. I wonder do i have to donwload the desktop beta client as well as the server beta client? I cant find that thing anywhere.Environment: Server: Windows Server 2008 R2Database: MySQLClient: Windows 7OC-Version: 6.0.0 beta1PHP-Version: 5.3.XRegards,Marcel Top RealRancor ownCloud master Posts: 17381 Joined: Sat May 26, 2012 3:00 pm ownCloud version: 9.0.2 Webserver: nginx Database: MySQL OS: Linux PHP version: 7.0.x Re: Client: 405 Method not Allowed Quote Postby RealRancor » Tue Nov 26, 2013 12:56 pm Hi,the "Method not allowed" message is a very common one (which can be found via the search function of the forums) and is mostly caused by a wrong server configuration. Because of this a FAQ thread was created:viewtopic.php?f=17&t=7536which contains every known workaround and some troubleshooting steps on how to debug this. *gone* Top marcel504 Newbie Posts: 7 Joined: Tue Nov 26, 2013 12:32 pm Webserver: IIS Database: MySQL OS: Windows Server PHP version: 5.3.X Re: Client: 405 Method not Allowed Quote Postby marcel504 » Tue Nov 26, 2013 12:59 pm Rancor wrote:Hi,the "Method not allowed" message is a very common one (which can be found via the
GoogleВойтиСкрытые поляПоиск групп или сообщений
/ Sign up EN English (EN) Русский (RU) Español (ES) Français (FR) Deutsch (DE) Nederlands (NL) Íslenska (IS) Eesti (ET) Қазақша (KK) Українська (UK) Dansk (DA) Català (CA) Polski (PL) Sign in / Sign up General Ideas 0 Under http://support.ajenti.org/topics/629-nginx-adding-http-verbs-405-method-not-allowed/ review Nginx adding HTTP verbs, 405 method not allowed Fabio Barone 2 years ago • updated by Eugene Pankov (Project coordinator) 2 years ago • 8 Not sure if this is ajenti related but I tried a lot else :)I created a web site in the ajenti panel. It's used to run owncloud. Owncloud supports WebDAV.I can successfully run owncloud from the web interface, that works perfectly, so the basic 405 method config works. However, when I try accessing owncloud through a webdav client, I get "405 method not allowed", and the access.log file shows that the client is trying to access with the OPTIONS http verb, and nginx returns 405.I tried some tutorials and added this entry to the instance's custom configuration:location / { #more stuff dav_access user:rw group:rw all:r; dav_methods PUT DELETE MKCOL COPY MOVE; dav_ext_methods PROPFIND OPTIONS;}This doesn't seem 405 method not to work though, so I am wondering if nginx doesn't even get to the instance's custom config and rejects these additional methods before...Any idea how I could enable these methods? Is there any such global config accessible through ajenti? Any additional hint/suggestion highly welcome. Vote 0 0 Undo Follow Replies 8 Oldest first Newest first Oldest first 0 Under review Eugene Pankov (Project coordinator) 2 years ago Hi Fabio,Put three dav_* directives into custom configuration of your Content entry, instead of general website's configuration. Reply Is it? Inappropriate Spam Duplicate | 0 Fabio Barone 2 years ago Eugene, thank you for responding so fast!Not sure I understood correctly:In the Content section of that site's configuration I have now:[^/]\.php(/|$) PHP FastCGIURL pattern: [^/]\.php(/|$) Regexand under "advanced", after your response, I added:location [^/]\.php(/|$) { dav_access user:rw group:rw all:r; dav_methods PUT DELETE MKCOL COPY MOVE; dav_ext_methods PROPFIND OPTIONS;}But it still does not work. Did I do something wrong here? Reply Is it? Inappropriate Spam Duplicate | 0 Eugene Pankov (Project coordinator) 2 years ago You don't need to add "location {" again when adding to a Content (location actually) custom configuration - Ajenti V puts the custom configuration inside the location { }. You can always verify the generated file by hand (/etc/nginx/conf.d/