Mailblocker

Results 21 comments of Mailblocker

Ah okay, could be since I'm using the plugin within a docker container the call `lpr` should be executed as `root`. Therefore I might not have any troubles with `lp`...

Can anyone give an advice how to debug/investigate this problem? I now ran into the problem that letsencrypt wont verify my certs anymore since I've sent too many requests. But...

The allowed number of requests is 50 per week, so I have to wait for at least a week. The thing is I have to fix the problem proxy(?) problem,...

@snkaupe I'm one step further, this link https://github.com/nginx-proxy/nginx-proxy/issues/1586#issuecomment-818238078 describes my problem and at least the proxy is now running again. Now I get the error 500 which indicates something between...

@0x47 have you read my comment here (https://github.com/nextcloud/docker/issues/1473#issuecomment-819772206) using a defined version for the nginx-proxy, does this solve the problem for you?

@unix0r can you elaborate how to see this behaviour? What are you looking at, ```docker-compose logs```? Edit: note to myself, I need a test setup for checking updates before doing...

@0x47 I don't know if your changes result in the same thing. The only line I changed was in the Dockerfile of the proxy changing this ```FROM jwilder/nginx-proxy:alpine``` to ```FROM...

For me the change worked so far that the warning/error: ```proxy_nginx | nginx: [emerg] no servers are inside upstream in /etc/nginx/conf.d/default.conf:68``` is no more present and the 503 error is...

@snkaupe Holy f***, I need to try this. Hopefully it will bring my cloud up again. In the last week I realized that I grew pretty dependend on the thing...

Resetting the owner of the files/directories doesn't fix my problem. Every access to my nextcloud instance results in this: ``` proxy_nginx | nginx.1 | MY_DOMAIN MY_IP - - [16/Apr/2021:20:08:11 +0000]...