Have been using WireGuard since 2 Years now it is really fast, it would be great to see it in Cloudron maybe with PiHole.

Hi,
i just wannted to ask about the Firewall in Cloudron Whitelist and Blocklisting IP's.
Usually i would do it over UFW but since its a bit diffrent in Cloudron.
Because i see some IP's thanks to shodan -.- trying to send some spams and i would like to block them.
And GEO IP Blocking as a feature would be nice, i think login to my.cloudron.com should be really high secured, i mean yes we have 2FA but if someone tries bruteforce attacks will not lead to something because of 2FA, but why create uneeded webservice requests.

looking really forward for PI-Hole and Wireguard really

@Mallewax i think this would lead also to new people using cloudron

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

@girish OK we will see the Result tomorrow br

Hi thanks for the Information any news or goals regarding firewall and security of Cloudron IP-Blocking or Fail2Ban maybe?

Are there any news Regarding Wireguard and Pihole in Cloudron?

@girish Sad to hear thath Pi-hole didn't workout but lets see how AdGuard is Thanks for your Work

@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

@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"}}

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

@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

@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 app

Is 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

@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

@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 ?

@savity Worked Perfekt Thanks

@girish Sad to hear thath Pi-hole didn't workout but lets see how AdGuard is Thanks for your Work

@girish OK we will see the Result tomorrow br