Hi,
im using the NextCloud CMD for syncing and i get the error of Anerror occurred while opening a folder Network access is disabled i solve this issue by terminating the whole project and start it again, surprisingly that on the release build this problem appears more often that the debug build,
im using QT 5.10.1 and im running the code on VS2017, here is the CMD outputs:
07-04 15:27:30:007 [ info sync.engine ]: Server ""
07-04 15:27:30:009 [ info sync.csync.csync ]: ## Starting local discovery ##
07-04 15:27:30:011 [ info sync.csync.csync ]: Update detection for local replica took 0.001 seconds walking 0 files
07-04 15:27:30:012 [ info sync.csync.csync ]: ## Starting remote discovery ##
07-04 15:27:30:014 [ info sync.accessmanager ]: 6 "PROPFIND" "http://**********" has X-Request-ID "************"
07-04 15:27:30:017 [ info sync.networkjob ]: OCC::LsColJob created for "http:**********" + "" "OCC::DiscoverySingleDirectoryJob"
07-04 15:27:30:020 [ warning sync.networkjob ]: QNetworkReply::NetworkError(UnknownNetworkError) "Network access is disabled." QVariant(Invalid)
07-04 15:27:30:022 [ info sync.networkjob.lscol ]: LSCOL of QUrl("http://**********************") FINISHED WITH STATUS QNetworkReply::NetworkError(UnknownNetworkError) "Network access is disabled."
07-04 15:27:30:024 [ warning sync.discovery ]: LSCOL job error "Network access is disabled." 0 QNetworkReply::NetworkError(UnknownNetworkError)
07-04 15:27:30:026 [ warning sync.csync.updater ]: opendir failed for - errno 5
07-04 15:27:30:027 [ warning sync.engine ]: ERROR during csync_update : "An error occurred while opening a folder Network access is disabled."
07-04 15:27:30:031 [ info sync.database ]: Closing DB "*********/._sync_369bd5743963.db"
07-04 15:27:30:037 [ info sync.engine ]: CSync run took 32 ms
how to solve this problem? and what part of the code is responsible of this issue?
Thanks
UPDATE:
the class the generates the error is networkjobs.cpp
Hi,
any updates about this issue?
I have the same problem with the 2.5 Windows Desktop release version. Have not found out why it happens.
Exactly the same problem here on Windows 10, with NC client 2.5.0v2.5.0 (build 20181112). I have to quit/restart NC client to get rid of the error message.
The problem does not occur for me on Linux (Fedora 29, with NC client 2.5).
I've found out by now that it seems to happen with 100% reproducibility after waking up from S3 standby. It may need to be asleep for a while to trigger the problem.
Here are some relevant info and maybe a duplicated bug report:
I've found out that when the error occurs, if I go in the parameters and I change the proxy from system to no proxy (and vice-versa), the error disappears, so I don't have to quit/restart the client. Not a solution of course, but maybe just a clue on what could be the problem.
I can confirm the proxy "trick" mentioned by @mlaverdiere
Additional details:
I don't know what happened but in the last few days the error didn't occur despite many suspend/standby resuming... I can't pinpoint what has changed on my system and I didn't change my NC configuration. I'll report back if I find something useful.
OK, the error is back unfortunately. Seems like an intermittent problem...
In my case it happens always after hibernation.
Happens for me too on Windows 10 x64
Can confirm this is happening with Nextcloud Desktop version 2.5.1final (build 20181204) using Windows 10 x64 1809
This happens after I upgraded the client from version 2.31 to 2.51. Normal boot everything is fine. After hibernation the client complains that network access is unavailable. Tried using system proxy but that makes no difference. Unfortunately I have not saved the 2.31 version which prevents me from downgrading. Thanks for all your effort on working on NextCloud services, much appreciated!
This happens after I upgraded the client from version 2.31 to 2.51. Normal boot everything is fine. After hibernation the client complains that network access is unavailable. Tried using system proxy but that makes no difference. Unfortunately I have not saved the 2.31 version which prevents me from downgrading. Thanks for all your effort on working on NextCloud services, much appreciated!
I have exactly the same problem. You can download older versions here : https://download.nextcloud.com/desktop/releases/Windows/
I've installed 2.3.3 (build 1) version, and it works.
I have the same problem. The proxy workaround works, but if I try to open the "Options" menu right after resuming from hibernation the Nextcloud app will crash without an error message. Version 2.5.1final (build 20181204) on Windows 10.
Same Problem over here! Win10x64 @NC Version 2.5.1final (build 20181204)
@mlaverdiere workaround helped for me too. No need to restart the client. But it is still freaking me out!
Also happening here on Windows 10
Checked this issue here: https://github.com/nextcloud/desktop/issues/865 just now and from a link there I downloaded 2.5.2 and that seems to have solved the problem so far.
Here's a link https://download.nextcloud.com/desktop/releases/Windows/Nextcloud-2.5.2-setup.exe
Fixed it with version 2.5.2!
Version 2.5.2git build 20190319.
I still have the issue.
[OCC::AccessManager::createRequest 6 "PROPFIND" "http://xxxx/nextcloud/remote.php/dav/files/xxxx/" has X-Request-ID "d9cbf639-5e11-4cbe-88c8-0d7e937ae5e0"
[OCC::AbstractNetworkJob::start OCC::PropfindJob created for "http://xxxx" + "/" "OCC::QuotaInfo"
[OCC::WebFlowCredentials::slotFinished request finished
[OCC::AbstractNetworkJob::slotFinished QNetworkReply::NetworkError(UnknownNetworkError) "Network access is disabled." QVariant(Invalid)
[OCC::WebFlowCredentials::stillValid QNetworkReply::NetworkError(UnknownNetworkError)
[OCC::WebFlowCredentials::stillValid "Network access is disabled."
[OCC::PropfindJob::finished PROPFIND of QUrl("http://xxxx/nextcloud/remote.php/dav/files/xxxx/") FINISHED WITH STATUS "UnknownNetworkError Network access is disabled."
[OCC::PropfindJob::finished *not* successful, http result code is 0 ""
Still same issue for me as well. NC 16.0.1 and Desktop 2.5.2
@jospoortvliet can this be tagged appropriately?
I am just having an install as proof of concept in a 3000 employees company + federation with partners and this one is really a show stopper.
i got some output from the nextcloud client.
I can 100% reproduce this issue by putting win10 pc to sleep and wakeup.
https://nopaste.xyz/?2f273d8a785c5d75#ivq6yCyA+MicH2+Wa3QBtTkKOp8k6ak9Y5m49EKbW3g=
Same issue here with 2.5.0, i just updated in 2.5.2, i'm gonna see if it solves the issue..
Looks like this does only happen with the portable version of 2.5.2.
Until yesterday I did use a just zip extracted version of the installer due to missing admin privileges.
Since yesterday I do have the nextcloud desktop client installed and the issue, that was 100% reproducable, is fixed.
I've never used the portable version and was still affected, so you're
probably just lucky.
On Mon, Jul 15, 2019, 14:36 vacy notifications@github.com wrote:
Looks like this does only happen with the portable version of 2.5.2.
Until yesterday I did use a just zip extracted version of the installer
due to missing admin privileges.
Since yesterday I do have the nextcloud desktop client installed and the
issue, that was 100% reproducable, is fixed.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/desktop/issues/482?email_source=notifications&email_token=AAG75BSURCGR3NFAJEOLHZLP7ROLPA5CNFSM4FINIF52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ5NRGY#issuecomment-511367323,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG75BX4OZEOWR5LRAY6MZLP7ROLPANCNFSM4FINIF5Q
.
You're right, it did work for consecutive 3 days and now ran into same issue. but in my experience the installed version actually performs better, never had a successful sync after windows hibernation before.
This error persists at the current version of nextcloud desktop. Is there any file count limitation, which can cause this problem?
I am having this issue on Version 2.6.4 stable and Windows 10. It seems to work well after fresh reboot or boot up but after waking from sleep I get the "An error occurred while opening a folder Network access is disabled" and my PC wont sync with my Freenas Nextcloud server? Any help would be appreciated.
Do you guys have windows software RAID? disk mirroring? we've a dozen pc's with win10 and only one with the disk mirror/raid1 is having that issue.
Hi, currently using version 3.01 with no issues.
Met vriendelijke groet,
Cees Bakker
06 3911 5106
TypeApp voor Android downloaden
Op 11 sep. 2020 16:13, om 16:13, vacy notifications@github.com schreef:
Do you guys have windows software RAID? disk mirroring? we've a dozen
pc's with win10 and only one with the disk mirror/raid1 is having that
issue.--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/nextcloud/desktop/issues/482#issuecomment-691119213
Thanks for letting us know, there's been adjustments and fixes around proxy handling indeed. Closing it then.
It's still not working properly. This bug crept up again in one of the last versions of the Windows desktop client. I'm currently using version 3.0.3. on two computers with Windows 10, and both are affected. After sleep or hibernation the network is gone. Restarting the client or toggeling the proxy helps.
I'm downgrading now to one or two versions to see when this bug appeared again...
Same here with version 3.0.3. Had no issues with 3.0.2.
Here's the relevant log. It seems to be the same issue as before - after waking from S3 NextCloud won't sync because of this error. It will keep failing every 30s until I flip the active proxy setting.
2020-11-11 08:13:35:526 [ info nextcloud.gui.folder ]: Trying to check "https://***/remote.php/dav/files/***/" for changes via ETag check. (time since last sync: 94 s)
2020-11-11 08:13:35:535 [ info nextcloud.sync.accessmanager ]: 6 "PROPFIND" "https://***/remote.php/dav/files/***/" has X-Request-ID "fd746d1d-ae9a-45b8-a33e-760adcd96e8a"
2020-11-11 08:13:35:536 [ warning nextcloud.sync.networkjob.etag ]: request network error: "Network access is disabled."
2020-11-11 08:13:35:536 [ info nextcloud.sync.networkjob ]: OCC::RequestEtagJob created for "https://***" + "/" "OCC::Folder"
2020-11-11 08:13:35:539 [ info nextcloud.sync.credentials.webflow ]: request finished
2020-11-11 08:13:35:540 [ warning nextcloud.sync.networkjob ]: QNetworkReply::UnknownNetworkError "Network access is disabled." QVariant(Invalid)
2020-11-11 08:13:35:540 [ warning nextcloud.sync.credentials.webflow ]: QNetworkReply::UnknownNetworkError
2020-11-11 08:13:35:540 [ warning nextcloud.sync.credentials.webflow ]: "Network access is disabled."
2020-11-11 08:13:35:541 [ info nextcloud.sync.networkjob.etag ]: Request Etag of QUrl("https://***/remote.php/dav/files/***/") FINISHED WITH STATUS "UnknownNetworkError Network access is disabled."
2020-11-11 08:14:04:017 [ info nextcloud.sync.accessmanager ]: 2 "" "https://***/ocs/v1.php/cloud/user?format=json" has X-Request-ID "fc7a9c89-a5e0-45fe-9470-ec0a4edef33d"
2020-11-11 08:14:04:018 [ info nextcloud.sync.networkjob ]: OCC::JsonApiJob created for "https://***" + "ocs/v1.php/cloud/user" "OCC::UserInfo"
2020-11-11 08:14:04:019 [ info nextcloud.sync.credentials.webflow ]: request finished
2020-11-11 08:14:04:020 [ warning nextcloud.sync.networkjob ]: QNetworkReply::UnknownNetworkError "Network access is disabled." QVariant(Invalid)
2020-11-11 08:14:04:020 [ warning nextcloud.sync.credentials.webflow ]: QNetworkReply::UnknownNetworkError
2020-11-11 08:14:04:020 [ warning nextcloud.sync.credentials.webflow ]: "Network access is disabled."
2020-11-11 08:14:04:021 [ info nextcloud.sync.networkjob.jsonapi ]: JsonApiJob of QUrl("https://***/ocs/v1.php/cloud/user?format=json") FINISHED WITH STATUS "UnknownNetworkError Network access is disabled."
2020-11-11 08:14:04:024 [ warning nextcloud.sync.networkjob.jsonapi ]: Network error: "ocs/v1.php/cloud/user" "Network access is disabled." QVariant(Invalid)
2020-11-11 08:14:04:024 [ info nextcloud.sync.accessmanager ]: 2 "" "https://***/remote.php/dav/avatars/***/128.png" has X-Request-ID "7a86dde9-b6f5-4922-9e82-db088ccb14ed"
2020-11-11 08:14:04:025 [ info nextcloud.sync.networkjob ]: OCC::AvatarJob created for "https://***" + "" "OCC::UserInfo"
2020-11-11 08:14:04:030 [ info nextcloud.sync.credentials.webflow ]: request finished
2020-11-11 08:14:04:031 [ warning nextcloud.sync.networkjob ]: QNetworkReply::UnknownNetworkError "Network access is disabled." QVariant(Invalid)
2020-11-11 08:14:04:031 [ warning nextcloud.sync.credentials.webflow ]: QNetworkReply::UnknownNetworkError
2020-11-11 08:14:04:032 [ warning nextcloud.sync.credentials.webflow ]: "Network access is disabled."
2020-11-11 08:14:05:512 [ info nextcloud.gui.folder ]: Trying to check "https://***/remote.php/dav/files/***/" for changes via ETag check. (time since last sync: 124 s)
2020-11-11 08:14:05:512 [ info nextcloud.sync.accessmanager ]: 6 "PROPFIND" "https://***/remote.php/dav/files/***/" has X-Request-ID "7917d58d-3933-4935-9e9a-292fa42da03d"
2020-11-11 08:14:05:512 [ warning nextcloud.sync.networkjob.etag ]: request network error: "Network access is disabled."
2020-11-11 08:14:05:512 [ info nextcloud.sync.networkjob ]: OCC::RequestEtagJob created for "https://***" + "/" "OCC::Folder"
2020-11-11 08:14:05:512 [ info nextcloud.sync.credentials.webflow ]: request finished
2020-11-11 08:14:05:512 [ warning nextcloud.sync.networkjob ]: QNetworkReply::UnknownNetworkError "Network access is disabled." QVariant(Invalid)
2020-11-11 08:14:05:512 [ warning nextcloud.sync.credentials.webflow ]: QNetworkReply::UnknownNetworkError
2020-11-11 08:14:05:512 [ warning nextcloud.sync.credentials.webflow ]: "Network access is disabled."
2020-11-11 08:14:05:512 [ info nextcloud.sync.networkjob.etag ]: Request Etag of QUrl("https://***/remote.php/dav/files/***/") FINISHED WITH STATUS "UnknownNetworkError Network access is disabled."
@er-vin could you please re-open?
Hi, we are facing the same problem here, since the 3.0.3 update (windows 10 v.20H2).
Hello, same problem here since 3.0.3 on Windows 2004 19041.630
2020-11-23 11:53:17:490 [ debug nextcloud.gui.account.state ] [ OCC::AccountState::checkConnectivity ]: "[email protected]" The last ETag check succeeded within the last 30 secs. No connection check needed!
2020-11-23 11:53:31:487 [ info nextcloud.gui.folder ]: Trying to check "https://nextcloud.mydomain.com/remote.php/dav/files/myuser/" for changes via ETag check. (time since last sync: 486 s)
2020-11-23 11:53:31:488 [ debug nextcloud.gui.folder.manager ] [ OCC::FolderMan::slotRunOneEtagJob ]: Scheduling "https://nextcloud.mydomain.com/remote.php/dav/files/myuser/" to check remote ETag
2020-11-23 11:53:31:488 [ info nextcloud.sync.accessmanager ]: 6 "PROPFIND" "https://nextcloud.mydomain.com/remote.php/dav/files/myuser/" has X-Request-ID "291f58ed-abbf-4dca-9c97-3dffe8f1199c"
2020-11-23 11:53:31:489 [ warning nextcloud.sync.networkjob.etag ]: request network error: "L'accès au réseau est désactivé."
2020-11-23 11:53:31:490 [ info nextcloud.sync.networkjob ]: OCC::RequestEtagJob created for "https://nextcloud.mydomain.com" + "/" "OCC::Folder"
2020-11-23 11:53:31:498 [ info nextcloud.sync.credentials.webflow ]: request finished
2020-11-23 11:53:31:499 [ warning nextcloud.sync.networkjob ]: QNetworkReply::UnknownNetworkError "L'accès au réseau est désactivé." QVariant(Invalid)
2020-11-23 11:53:31:499 [ warning nextcloud.sync.credentials.webflow ]: QNetworkReply::UnknownNetworkError
2020-11-23 11:53:31:499 [ warning nextcloud.sync.credentials.webflow ]: "L'accès au réseau est désactivé."
2020-11-23 11:53:31:499 [ info nextcloud.sync.networkjob.etag ]: Request Etag of QUrl("https://nextcloud.mydomain.com/remote.php/dav/files/myuser/") FINISHED WITH STATUS "UnknownNetworkError L'accès au réseau est désactivé."
2020-11-23 11:53:31:499 [ debug nextcloud.sync.networkjob ] [ OCC::AbstractNetworkJob::slotFinished ]: Network job OCC::RequestEtagJob finished for "/"
EDIT : I downgraded to version 3.0.2, working fine.
Same here. Rolling back to 3.0.2 now.
Same issue over here, Windows 10 and client 3.0.3. Just installed client 3.1.0 and lets wait and see what happens.
Can confirm the same issue for 3.1.0 unfortunately. Will also roll back to 3.0.2.
I was suddenly having this error after upgrading from the 3.1.0 exe installer to the 3.1.0 msi installer, as I understood that is the way Nextcloud is going.
After thatr, every time my laptop resumes after standby, I see a big red cross and this error is shown in the log. Sync is only resumed after killing Nextcloud desktop, then starting it up again (or rebooting my laptop).
I thought it was something with 3.1.0, so downgrade to 3.0.3 msi installer. This showed exactly the same issue.
Then changed again to 3.0.3 exe installer: all issues disappeared,
The upgraded to 3.1.0 exe installer: again no issues.
So to me it seems the msi installer does something differently than the exe installer. Maybe it's a permission thing?
OK, this is odd, but thanks for the information.
I was suddenly having this error after upgrading from the 3.1.0 exe installer to the 3.1.0 msi installer, as I understood that is the way Nextcloud is going.
After thatr, every time my laptop resumes after standby, I see a big red cross and this error is shown in the log. Sync is only resumed after killing Nextcloud desktop, then starting it up again (or rebooting my laptop).
I thought it was something with 3.1.0, so downgrade to 3.0.3 msi installer. This showed exactly the same issue.Then changed again to 3.0.3 exe installer: all issues disappeared,
The upgraded to 3.1.0 exe installer: again no issues.So to me it seems the msi installer does something differently than the exe installer. Maybe it's a permission thing?
I can confirm this behavior on my Windows 10 laptop. Installed 3.1.0. exe and works perfect.
Problem still present in version 3.1.1
3.1.1 running on Windows 10 x64 20H2 here. Server is 19.0.6
I can confirm that the MSI installer is giving this "Network Access is disabled" error after network changes (either due to sleep/resume or VPN client opening/closing a tunnel). Going back to the EXE installer solved the issue.
I then compared the resulting files of both installers (in %ProgramFiles%). The following files have different SHA-1 signature, but the exact same version info and size:
More interestingly, the MSI installer contains this single additional file:
Version of this file is 5.12.9.0
I would guess this might be the culprit.
Installed 3.1.1 client with msi-installer and had red-X after hibernate/resume (Win10 2004, 20.0.4 server in local network). Uninstalled and installed 3.1.1 with exe-installer. No problem after hibernate/resume.
Most helpful comment
Installed 3.1.1 client with msi-installer and had red-X after hibernate/resume (Win10 2004, 20.0.4 server in local network). Uninstalled and installed 3.1.1 with exe-installer. No problem after hibernate/resume.