@girish It didn't worked for 4 Days now in a row
Posts made by savity
-
RE: Backup Fails NEXTCLOUD
@girish and some time a go you have given me a soluton:
@savity Can you try this change https://git.cloudron.io/cloudron/box/-/commit/bedcd6fccf58830b316318699375bc1f582a5d7a ? The file on Cloudron is /home/yellowtent/box/src/storage/s3.js. Essentially change the timeout from 3000 * 1000 to 0. And also change maxRetries to 10. You don't need to restart anything after the change since the code changes are immediately picked up.
I am using MINIO as Backup and i think this all started after the last Ubuntu security update
-
RE: Backup Fails NEXTCLOUD
@girish there was really no error but since theni raised the backup RAM and it worked for 1 Week.
Now i got a new error
Jan 19 02:11:14 box:tasks 2859: {"percent":51,"message":"Uploading backup 4473M@7MBps (SERVER.domain.domain)"}
Jan 19 02:11:20 box:shell backup-snapshot/APP_ID (stdout): 2021-01-19T01:11:20.928Z box:storage/s3 Error uploading [SERVER/snapshot/APP_ID.tar.gz.enc]: s3 upload error. { InternalError: We encountered an internal error, please try again.
at Request.extractError (/home/yellowtent/box/node_modules/aws-sdk/lib/services/s3.js:837:35)
at Request.callListeners (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:688:14)
at Request.transition (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/home/yellowtent/box/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /home/yellowtent/box/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:690:12)
at Request.callListeners (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
message: 'We encountered an internal error, please try again.',
code: 'InternalError',
region: null,
time: 2021-01-19T01:11:20.924Z,
requestId: '165B7CF26E4F51D8',
extendedRequestId: undefined,
cfId: undefined,
statusCode: 500,
retryable: true }
Jan 19 02:11:20 box:shell backup-snapshot/APP_ID (stdout): 2021-01-19T01:11:20.929Z box:backupupload upload completed. error: { BoxError: Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError
at ManagedUpload.callback (/home/yellowtent/box/src/storage/s3.js:130:33)
at ManagedUpload.cleanup (/home/yellowtent/box/node_modules/aws-sdk/lib/s3/managed_upload.js:629:10)
at Response.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/s3/managed_upload.js:566:28)
at Request.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:369:18)
at Request.callListeners (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:688:14)
at Request.transition (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/home/yellowtent/box/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /home/yellowtent/box/node_modules/aws-sdk/lib/state_machine.js:26:10
name: 'BoxError',
reason: 'External Error',
details: {},
message:
'Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError' }
Jan 19 02:11:20 box:backups runBackupUpload: result - {"result":"Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError"}
Jan 19 02:11:21 box:shell backup-snapshot/APP_ID code: 50, signal: null
Jan 19 02:11:21 box:backups SERVER.domain.domain Unable to backup { BoxError: Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError
at /home/yellowtent/box/src/backups.js:874:29
at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)
at ChildProcess.emit (events.js:198:13)
at ChildProcess.EventEmitter.emit (domain.js:448:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
name: 'BoxError',
reason: 'External Error',
details: {},
message:
'Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError' }
Jan 19 02:11:21 box:taskworker Task took 680.211 seconds
Jan 19 02:11:21 box:tasks setCompleted - 2859: {"result":null,"error":{"stack":"BoxError: Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError\n at /home/yellowtent/box/src/backups.js:874:29\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)\n at ChildProcess.emit (events.js:198:13)\n at ChildProcess.EventEmitter.emit (domain.js:448:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"External Error","details":{},"message":"Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError"}}
Jan 19 02:11:21 box:tasks 2859: {"percent":100,"result":null,"error":{"stack":"BoxError: Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError\n at /home/yellowtent/box/src/backups.js:874:29\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)\n at ChildProcess.emit (events.js:198:13)\n at ChildProcess.EventEmitter.emit (domain.js:448:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"External Error","details":{},"message":"Error uploading SERVER/snapshot/APP_ID.tar.gz.enc. Message: We encountered an internal error, please try again. HTTP Code: InternalError"}} -
Backup Fails NEXTCLOUD
Hi failing backups since 7 Days in a row
it only not work with Nextcloud 4 other apps do work
Cloudron 6.0.1
But i don't see any errors in the Backup Logs?
BR
Savity -
RE: Adding custom dns server
@girish installed new
did not work with the password 7uxY@UbvhF9Q4rANNGLxSSG#s2bg29$j but it worked with password123! maybe a bug....
Yeah i know on the terminal
Looks like this pw works
7uxY@UbvhF9Q4rANNGLxSSG#s2bg29
and this not
7uxY@UbvhF9Q4rANNGLxSSG#s2bg29$j -
RE: Adding custom dns server
@girish Thanks id like to but changing the password , does not work in ADGuard
1.)htpasswd -nbB admin mypassword -> Creating a password
2.) copying my result to /app/data/AdGuardHome.yaml restarting the appIs there any issue ? i have reproduced it several times, can't change it
Normally i don't post passwords but in this case you can test it with 7uxY@UbvhF9Q4rANNGLxSSG#s2bg29$j
Because its not productiv enviroment.
This app packages AdGuard Home 0.104.3.
BR
-
Adding custom dns server
@girish regarding this i would use my internal openvpn APP to use the DNS server from ADGuard where i only whitelist the openVPN client ip.
But in the documentation there is a link regarding internal DNS, witch is not working:
https://docs.cloudron.io/apps/openvpn/Still you know i have made server topics regarding WireGuard and Raspberry PI, still thinks its better.
But id like to try first oPenVPN with Ad Guard
BR
-
RE: Adding custom dns server
@girish I think i explained it wrong
I have 2 Apps openVPN and and ADGuard what is the correct way to tell openVPN to use the dns from the ADGuard service ?
-
RE: Pi Hole - network-wide ad blocking
@girish Sad to hear thath Pi-hole didn't workout but lets see how AdGuard is
Thanks for your Work
-
RE: Pi Hole - network-wide ad blocking
Are there any news Regarding Wireguard and Pihole in Cloudron?
-
Backup issues with minio
Since 1 Week every 2 Day its not Possible to create Backups.
What i don't understand is why every 2 Days. And it only happens with Part 60.
Cloudron Version: v5.6.3
Nov 11 10:18:09 box:storage/s3 copy: s3 copy error when copying bulut/snapshot/app_5b67e84d-40da-4604-80ec-45e8d610c839.tar.gz.enc: TimeoutError: Connection timed out after 600000ms
Nov 11 10:18:09 box:tasks 2362: {"percent":51,"message":"Copied 1 files with error: BoxError: Error copying NAME/snapshot/app_5b67e84d-40da-4604-80ec-45e8d610c839.tar.gz.enc (68594108692 bytes): TimeoutError TimeoutError: Connection timed out after 600000ms (name.name.name)"}
Nov 11 10:18:09 box:backups name.name.name Unable to backup { BoxError: Error copying name/snapshot/app_5b67e84d-40da-4604-80ec-45e8d610c839.tar.gz.enc (68594108692 bytes): TimeoutError TimeoutError: Connection timed out after 600000ms
at done (/home/yellowtent/box/src/storage/s3.js:247:52)
at Response.s3.abortMultipartUpload (/home/yellowtent/box/src/storage/s3.js:324:75)
at Request.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:369:18)
at Request.callListeners (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/home/yellowtent/box/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:688:14)
at Request.transition (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/home/yellowtent/box/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /home/yellowtent/box/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/home/yellowtent/box/node_modules/aws-sdk/lib/request.js:38:9)
name: 'BoxError',
reason: 'External Error',
details: {},
message:
'Error copying name/snapshot/app_5b67e84d-40da-4604-80ec-45e8d610c839.tar.gz.enc (68594108692 bytes): TimeoutError TimeoutError: Connection timed out after 600000ms' } -
RE: New Firewall Feature issues
Looks like it depends on the server ressources maybe.
-
RE: New Firewall Feature issues
First i Importet
https://www.ipdeny.com/ipblocks/
RUSSIAN FEDERATION (RU) [download ru.zone] Size: 170 KB (10497 IP blocks)
And after Importing
CHINA (CN) [download cn.zone] Size: 136 KB (8444 IP blocks)
The issues startet
-
New Firewall Feature issues
Hi,
was happy about the new Firewall Feature so i started Blocking by Countrys.
Blocked China and Russia IPs.
So then at a Point i get the message Response timeout.
Now i am not abel to Delete any IP or add new IP. I always get the Response timeout.
So i checked the box.log it tells me the IP's are duplicated
Box POST /api/v1/network/blocklist 500 Internal Server Error Response timeout 20001.781 ms - 72
2020-09-12T07:43:00.057Z box:shell setBlocklist (stdout): ipset v6.34: Element cannot be added to the set: it's already added2020-09-12T07:43:00.060Z box:shell setBlocklist code: 1, signal: null
ERROR HttpError: Error setting blocklist: setBlocklist exited with code 1 signal null
at Function.BoxError.toHttpError (/home/yellowtent/box/src/boxerror.js:97:16)
at /home/yellowtent/box/src/routes/network.js:29:41
at /home/yellowtent/box/src/network.js:45:27
at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)
at ChildProcess.emit (events.js:198:13)
at ChildProcess.EventEmitter.emit (domain.js:448:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12) [ /home/yellowtent/box/node_modules/express/lib/application.js:630:43 ]So i deleted the List and pasted everything again now i am getting
Box POST /api/v1/network/blocklist 500 Internal Server Error Response timeout 20001.588 ms - 72
ERROR [object Object] [ /home/yellowtent/box/node_modules/express/lib/application.js:630:43 ]I will check the list on duplicates but, is there any Limits on IP Addresses or how much you can configure for the first time?
Best Regards -
RE: Pi Hole - network-wide ad blocking
@Mallewax i think this would lead also to new people using cloudron
-
RE: Pi Hole - network-wide ad blocking
yeah i mean it would be for me
i would never create pihole acessable for others its for private reasons vpn+pihole. So pihole would be listening, lets say on 10.9.0.0
Maybe in the future the idea could to configure other apps only availaie in the same VPN Network