daemoncesar Postado Janeiro 17 Compartilhar Postado Janeiro 17 Alguém já utilizou o owncloud com cmd ? Fica bom enviar diretamente do console os arquivos ? 0 Citar Link para o comentário Compartilhar em outros sites More sharing options...
Administração AngelCosta Postado Janeiro 19 Administração Compartilhar Postado Janeiro 19 Pelo console nunca tentei... mas é hospedado em servidor seu? Se for, deve ser tranquilo e sem problema, supondo q seu servidor não tenha um problema de rede... 0 Citar 'Cause he's my best friend, he's my pal. He's my homeboy, my rotten soldier. He's my sweet cheese. My good-time boy. Link para o comentário Compartilhar em outros sites More sharing options...
daemoncesar Postado Janeiro 19 Autor Compartilhar Postado Janeiro 19 ambos servidores é meu. 0 Citar Link para o comentário Compartilhar em outros sites More sharing options...
daemoncesar Postado Janeiro 19 Autor Compartilhar Postado Janeiro 19 01-19 15:55:00:833 [ info sync.csync.csync ]: ## Starting remote discovery ## 01-19 15:55:00:833 [ info sync.accessmanager ]: 6 "PROPFIND" "https://cloud.dominio.com/remote.php/dav/files/dominio/" has X-Request-ID "ef7cb292-2625-482d-87e0-0874c85e74f8" 01-19 15:55:00:834 [ info sync.networkjob ]: OCC::LsColJob created for "https://cloud.dominio.com" + "" "OCC::DiscoverySingleDirectoryJob" 01-19 15:55:00:865 [ warning sync.networkjob ]: QNetworkReply::ContentAccessDenied "Server replied \"403 Forbidden\" to \"PROPFIND https://cloud.dominio.com/remote.php/dav/files/dominio/\"" QVariant(int, 403) 01-19 15:55:00:865 [ info sync.networkjob.lscol ]: LSCOL of QUrl("https://cloud.dominio.com/remote.php/dav/files/dominio/") FINISHED WITH STATUS "ContentAccessDenied Server replied \"403 Forbidden\" to \"PROPFIND https://cloud.dominio.com/remote.php/dav/files/dominio/\"" 01-19 15:55:00:865 [ warning sync.discovery ]: LSCOL job error "Error transferring https://cloud.dominio.com/remote.php/dav/files/dominio/ - server replied: Forbidden" 403 QNetworkReply::ContentAccessDenied 01-19 15:55:00:866 [ warning sync.csync.updater ]: Directory access Forbidden (File Firewall?) 01-19 15:55:00:866 [ warning sync.engine ]: ERROR during csync_update : "An error occurred while opening a folder : Error transferring https://cloud.dominio.com/remote.php/dav/files/dominio/ - server replied: Forbidden" 01-19 15:55:00:866 [ info sync.database ]: Closing DB "/usr/local/teste/._sync_ba29c7f389aa.db" 01-19 15:55:00:868 [ info sync.engine ]: CSync run took 37 ms 01-19 15:55:00:869 [ info sync.database ]: Closing DB "/usr/local/teste/._sync_ba29c7f389aa.db" O Erro final é este. opa.. em files é o nome do usuário. Na hora de colar não verifiquei. 0 Citar Link para o comentário Compartilhar em outros sites More sharing options...
Administração AngelCosta Postado Janeiro 19 Administração Compartilhar Postado Janeiro 19 Bom, eu uso o nextcloud, mas lá no fórum deles alguém apontou algum erro de proxy: https://help.nextcloud.com/t/an-error-occured-while-opening-a-folder-operation-canceled/32994/13 0 Citar 'Cause he's my best friend, he's my pal. He's my homeboy, my rotten soldier. He's my sweet cheese. My good-time boy. Link para o comentário Compartilhar em outros sites More sharing options...
daemoncesar Postado Janeiro 19 Autor Compartilhar Postado Janeiro 19 Achei o owncloud mais leve e objetivo. Só preciso para arquivos. 0 Citar Link para o comentário Compartilhar em outros sites More sharing options...
daemoncesar Postado Janeiro 20 Autor Compartilhar Postado Janeiro 20 Em 19/01/2024 em 13:30, AngelCosta disse: Bom, eu uso o nextcloud, mas lá no fórum deles alguém apontou algum erro de proxy: https://help.nextcloud.com/t/an-error-occured-while-opening-a-folder-operation-canceled/32994/13 Eu testei o nextcloud, mas ele é bem mais pesado que o owncloud. Eu só preciso para arquivos mesmo... O owncloud rodou com 1GB de ram, já o nextcloud apanhou bastante. 0 Citar Link para o comentário Compartilhar em outros sites More sharing options...
daemoncesar Postado Janeiro 20 Autor Compartilhar Postado Janeiro 20 Pior que com o nextcloud consigo compiar por cmd. 0 Citar Link para o comentário Compartilhar em outros sites More sharing options...
daemoncesar Postado Janeiro 21 Autor Compartilhar Postado Janeiro 21 não funcionou. nao sei mais o que fazer para usar o owncloudcmd. 01-21 17:40:09:657 [ info sync.csync.updater ]: Checking for rename based on inode # 1434 01-21 17:40:09:657 [ info sync.csync.updater ]: file: iproute2/rt_protos, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:657 [ info sync.csync.updater ]: Checking for rename based on inode # 1429 01-21 17:40:09:657 [ info sync.csync.updater ]: file: iproute2/bpf_pinning, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:657 [ info sync.csync.updater ]: Checking for rename based on inode # 1430 01-21 17:40:09:657 [ info sync.csync.updater ]: file: iproute2/ematch_map, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:657 [ info sync.csync.updater ]: Checking for rename based on inode # 317 01-21 17:40:09:657 [ info sync.csync.updater ]: file: iproute2/rt_protos.d, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:658 [ info sync.csync.updater ]: Checking for rename based on inode # 1438 01-21 17:40:09:658 [ info sync.csync.updater ]: file: iproute2/rt_protos.d/README, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:658 [ info sync.csync.updater ]: <= Closing walk for /etc/iproute2/rt_protos.d with read_from_db 0 01-21 17:40:09:658 [ info sync.csync.updater ]: Checking for rename based on inode # 1435 01-21 17:40:09:658 [ info sync.csync.updater ]: file: iproute2/rt_realms, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:658 [ info sync.csync.updater ]: Checking for rename based on inode # 1437 01-21 17:40:09:658 [ info sync.csync.updater ]: file: iproute2/rt_tables, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:658 [ info sync.csync.updater ]: Checking for rename based on inode # 1431 01-21 17:40:09:658 [ info sync.csync.updater ]: file: iproute2/group, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:658 [ info sync.csync.updater ]: Checking for rename based on inode # 1433 01-21 17:40:09:658 [ info sync.csync.updater ]: file: iproute2/rt_dsfield, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:658 [ info sync.csync.updater ]: Checking for rename based on inode # 1436 01-21 17:40:09:658 [ info sync.csync.updater ]: file: iproute2/rt_scopes, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:658 [ info sync.csync.updater ]: Checking for rename based on inode # 318 01-21 17:40:09:658 [ info sync.csync.updater ]: file: iproute2/rt_tables.d, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:659 [ info sync.csync.updater ]: Checking for rename based on inode # 1439 01-21 17:40:09:659 [ info sync.csync.updater ]: file: iproute2/rt_tables.d/README, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:659 [ info sync.csync.updater ]: <= Closing walk for /etc/iproute2/rt_tables.d with read_from_db 0 01-21 17:40:09:659 [ info sync.csync.updater ]: Checking for rename based on inode # 1432 01-21 17:40:09:659 [ info sync.csync.updater ]: file: iproute2/nl_protos, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:659 [ info sync.csync.updater ]: <= Closing walk for /etc/iproute2 with read_from_db 0 01-21 17:40:09:659 [ info sync.csync.updater ]: Checking for rename based on inode # 2109548 01-21 17:40:09:659 [ info sync.csync.updater ]: file: avahi, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:659 [ info sync.csync.updater ]: Checking for rename based on inode # 2109549 01-21 17:40:09:659 [ info sync.csync.updater ]: file: avahi/avahi-daemon.conf, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:659 [ info sync.csync.updater ]: Checking for rename based on inode # 2109551 01-21 17:40:09:659 [ info sync.csync.updater ]: file: avahi/services, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:660 [ info sync.csync.updater ]: <= Closing walk for /etc/avahi/services with read_from_db 0 01-21 17:40:09:660 [ info sync.csync.updater ]: Checking for rename based on inode # 2109550 01-21 17:40:09:660 [ info sync.csync.updater ]: file: avahi/hosts, instruction: INSTRUCTION_NEW <<= 01-21 17:40:09:660 [ info sync.csync.updater ]: <= Closing walk for /etc/avahi with read_from_db 0 01-21 17:40:09:660 [ info sync.csync.updater ]: <= Closing walk for /etc with read_from_db 0 01-21 17:40:09:660 [ info sync.csync.csync ]: Update detection for local replica took 1.214 seconds walking 2155 files 01-21 17:40:09:660 [ info sync.csync.utils ]: Memory: 449796K total size, 26120K resident, 22988K shared 01-21 17:40:09:660 [ info sync.csync.csync ]: ## Starting remote discovery ## 01-21 17:40:09:661 [ info sync.accessmanager ]: 6 "PROPFIND" "https://cesar:[email protected]/remote.php/dav/files/cesar/" has X-Request-ID "f11517f6-a5d8-4cdc-8d85-189e9f497f17" 01-21 17:40:09:661 [ info sync.networkjob ]: OCC::LsColJob created for "https://cloud.domain.com" + "" "OCC::DiscoverySingleDirectoryJob" 01-21 17:40:09:706 [ warning sync.networkjob ]: QNetworkReply::ContentAccessDenied "Server replied \"403 Forbidden\" to \"PROPFIND https://[email protected]/remote.php/dav/files/cesar/\"" QVariant(int, 403) 01-21 17:40:09:706 [ info sync.networkjob.lscol ]: LSCOL of QUrl("https://[email protected]/remote.php/dav/files/cesar/") FINISHED WITH STATUS "ContentAccessDenied Server replied \"403 Forbidden\" to \"PROPFIND https://[email protected]/remote.php/dav/files/cesar/\"" 01-21 17:40:09:707 [ warning sync.discovery ]: LSCOL job error "Error transferring https://cesar:[email protected]/remote.php/dav/files/cesar/ - server replied: Forbidden" 403 QNetworkReply::ContentAccessDenied 01-21 17:40:09:707 [ warning sync.csync.updater ]: Directory access Forbidden (File Firewall?) 01-21 17:40:09:707 [ warning sync.engine ]: ERROR during csync_update : "An error occurred while opening a folder : Error transferring https://cesar:[email protected]/remote.php/dav/files/cesar/ - server replied: Forbidden" 01-21 17:40:09:708 [ info sync.database ]: Closing DB "/etc/._sync_20e10836eb9f.db" 01-21 17:40:09:708 [ info sync.engine ]: CSync run took 1263 ms 01-21 17:40:09:708 [ info sync.database ]: Closing DB "/etc/._sync_20e10836eb9f.db" 0 Citar Link para o comentário Compartilhar em outros sites More sharing options...
daemoncesar Postado Janeiro 22 Autor Compartilhar Postado Janeiro 22 vou ser obrigado a migrar para o nextcloud. 0 Citar Link para o comentário Compartilhar em outros sites More sharing options...
Posts Recomendados
Participe da conversa
Você pode postar agora e se cadastrar mais tarde. Se você tem uma conta, faça o login para postar com sua conta.