You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know PydioSync is not being developed any further, as Pydio has moved to CellSync officially, however, I am still running some Pydio 8 servers and would like to leverage PydioSync for them.
When running the Pydio UI and attempting to connect to an SSL server, the pydio-agent processes immediately crash. Event log reports the following error:
The operating system is Windows 10 Home, Version 2004. Would appreciate some assistance with this issue - haven't seen it before on any computers, and the error being reported is vague enough that I'm not sure where to go with it.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi all,
I know PydioSync is not being developed any further, as Pydio has moved to CellSync officially, however, I am still running some Pydio 8 servers and would like to leverage PydioSync for them.
When running the Pydio UI and attempting to connect to an SSL server, the pydio-agent processes immediately crash. Event log reports the following error:
Faulting application name: pydio-agent.exe, version: 0.0.0.0, time stamp: 0x5121fefe
Faulting module name: _ssl.pyd, version: 0.0.0.0, time stamp: 0x5560ae5d
Exception code: 0xc0000005
Fault offset: 0x0000000000098a23
Faulting process id: 0xe30
Faulting application start time: 0x01d6f2ca2175228d
Faulting application path: C:\PROGRA
2\PYDIOS1\bin\pydio-agent.exeFaulting module path: C:\Users\STEPHA~1\AppData\Local\Temp_MEI32042_ssl.pyd
Report Id: a870d9c7-0fac-4a57-b935-a9bdb9a7fb5b
Faulting package full name:
Faulting package-relative application ID:
The operating system is Windows 10 Home, Version 2004. Would appreciate some assistance with this issue - haven't seen it before on any computers, and the error being reported is vague enough that I'm not sure where to go with it.
Thanks!
The text was updated successfully, but these errors were encountered: