Try add in your nginx "vhost" as the first line:
Alias /.well-known/acme-challenge /path/to/acme/.well-known/acme-challenge
ProxyPassMatch ^/\.well-known !
I have this same error with ProxyPass inside apache vhost which proxying to
node application backend. In letsencrypt logs I have this same
Hello,
I am trying to get Dovecot 2.3.1 to track lastlogins of users. I'm
using a MySQL database. When I log in I am getting this in the error
log:
2018-04-02 18:24:21 imap(u...@domain.com)<61855><6R0rDeVodcl/AAAB>:
Error: last_login_dict: Failed to write value for user
u...@domain.com:
Hi
[This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at distinct
servers.]
I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error
messages at server1 (and vice versa at server2) as follows:
| Apr 2 17:12:18 server1.lan dovecot: doveadm: Error:
> On 02 April 2018 at 19:19 Ricardo Machini Barbosa
> wrote:
>
>
> Hello,
>
>
>
> After update dovecot from 2.3.0.1 to 2.3.1 the doveadm backup stopped to
> work.
>
>
>
> Command line:
>
> doveadm -D backup -u em...@dominio.com.br -R tcp:mailsrv01:9011
>
>
Hello,
After update dovecot from 2.3.0.1 to 2.3.1 the doveadm backup stopped to
work.
Command line:
doveadm -D backup -u em...@dominio.com.br -R tcp:mailsrv01:9011
I updated dovecot on mailsrv01 to 2.3.1.
Process on mailsrv01 (the count message stop and process stay this way until
Am 02.04.2018 um 14:25 schrieb Jeff Abrahamson:
I'm handling mail for several domains, let's call them a.com, b.com,
and c.com. I have certificates for each of these domains individually
via certbot (letsencrypt) and nginx is happy with all of that.
Since I initially configured the site to
On Mon, Apr 02, 2018 at 04:20:05PM +0300, Reio Remma wrote:
> On 02.04.18 16:17, Jeff Abrahamson wrote:
> > On Mon, Apr 02, 2018 at 02:34:34PM +0200, Gedalya wrote:
> > > You have a problem with your nginx config. It doesn't seem
> > > related to postfix et al.
> > >
> > > Really off-topic for
On 04/02/2018 03:17 PM, Jeff Abrahamson wrote:
> On Mon, Apr 02, 2018 at 02:34:34PM +0200, Gedalya wrote:
>> On 04/02/2018 02:25 PM, Jeff Abrahamson wrote:
>>> I see that the file
>>>
>>> .well-known/acme-challenge/IT7-YURAep4bniD9zYpKpdRUBQcgCRJ6FflmZzWQGNg
>>>
>>> is being created (and one
On 02.04.18 16:17, Jeff Abrahamson wrote:
On Mon, Apr 02, 2018 at 02:34:34PM +0200, Gedalya wrote:
On 04/02/2018 02:25 PM, Jeff Abrahamson wrote:
I see that the file
.well-known/acme-challenge/IT7-YURAep4bniD9zYpKpdRUBQcgCRJ6FflmZzWQGNg
is being created (and one other file, too) but
On Mon, Apr 02, 2018 at 02:34:34PM +0200, Gedalya wrote:
> On 04/02/2018 02:25 PM, Jeff Abrahamson wrote:
> > I see that the file
> >
> > .well-known/acme-challenge/IT7-YURAep4bniD9zYpKpdRUBQcgCRJ6FflmZzWQGNg
> >
> > is being created (and one other file, too) but that nginx reports that
> >
On 04/02/2018 02:25 PM, Jeff Abrahamson wrote:
> I see that the file
>
> .well-known/acme-challenge/IT7-YURAep4bniD9zYpKpdRUBQcgCRJ6FflmZzWQGNg
>
> is being created (and one other file, too) but that nginx reports that
> the _directory_
>
>
I'm handling mail for several domains, let's call them a.com, b.com,
and c.com. I have certificates for each of these domains individually
via certbot (letsencrypt) and nginx is happy with all of that.
Since I initially configured the site to handle mail only for a.com,
my /etc/postfix/main.cf
12 matches
Mail list logo