We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Roundcube: Connection to storage server failed
Roundcube: Connection to storage server failed
Hello,
Can anyone please help to fix this problem?
Roundcube: Connection to storage server failed
Centos 7
Can anyone please help to fix this problem?
Roundcube: Connection to storage server failed
Centos 7
Re: Roundcube: Connection to storage server failed
No one here who can help or fix this?
Re: Roundcube: Connection to storage server failed
I am using Roundcube without any problems, so you probably want to provide details of your error messages so people can help you.
Re: Roundcube: Connection to storage server failed
Hello,
This is the error message i get when i wan to login to webmail on centos 7 installation:
"Connection to storage server failed"
This is the error message i get when i wan to login to webmail on centos 7 installation:
"Connection to storage server failed"
Re: Roundcube: Connection to storage server failed
Not sure if you are having the same problem I had or not, but after having the same message and looking at my logs I found the issue was with Dovecot. I did an update of the system and something with Dovecot changed. Namespace issues. Here is what I did:
edit /etc/dovecot/dovecot.conf using vim/vi/nano (whatever you prefer)
Add the following:
namespace inbox {
inbox = yes
}
I can't say for sure this is the same problem you are having, but if you check your dovecot.log (/var/logs/dovecot.log) and you see the below error messages then try out that fix.
imap([email protected]): Error: user [email protected]: Initialization failed: namespace configuration error: inbox=yes namespace missing
edit /etc/dovecot/dovecot.conf using vim/vi/nano (whatever you prefer)
Add the following:
namespace inbox {
inbox = yes
}
I can't say for sure this is the same problem you are having, but if you check your dovecot.log (/var/logs/dovecot.log) and you see the below error messages then try out that fix.
imap([email protected]): Error: user [email protected]: Initialization failed: namespace configuration error: inbox=yes namespace missing
Re: Roundcube: Connection to storage server failed
Thank you so much @Thantis.
It works now :) You saved my day :)
It works now :) You saved my day :)
Thantis wrote:Not sure if you are having the same problem I had or not, but after having the same message and looking at my logs I found the issue was with Dovecot. I did an update of the system and something with Dovecot changed. Namespace issues. Here is what I did:
edit /etc/dovecot/dovecot.conf using vim/vi/nano (whatever you prefer)
Add the following:
namespace inbox {
inbox = yes
}
I can't say for sure this is the same problem you are having, but if you check your dovecot.log (/var/logs/dovecot.log) and you see the below error messages then try out that fix.
imap([email protected]): Error: user [email protected]: Initialization failed: namespace configuration error: inbox=yes namespace missing
Re: Roundcube: Connection to storage server failed
I faced the same issue on CentOS 7 + VESTA and I confirm that the solution provided by Thantis works :-)
BTW, you might want to make this change to /etc/dovecot/conf.d/10-mail.conf where namespaces are supposed o be defined.
BTW, you might want to make this change to /etc/dovecot/conf.d/10-mail.conf where namespaces are supposed o be defined.
Re: Roundcube: Connection to storage server failed
Wonderful, it works
-
- Posts: 12
- Joined: Wed Oct 29, 2014 9:54 am
- Os: CentOS 6x
- Web: apache + nginx
Re: Roundcube: Connection to storage server failed
Thanks, This work for me too :)
Re: Roundcube: Connection to storage server failed
This works on login , but I'm still face error say :
An error occurred!
SMTP Error: [451] Temporary local problem - please try later
An error occurred!
SMTP Error: [451] Temporary local problem - please try later