Roundcube over ipv6 not working

sysdev

Verified User
Joined
Jul 16, 2007
Messages
379
On my server ipv6 works correctly for all domains and for the server host itself, but when I browse to
https://servername/roundcube/ or /webmail/ it returns a 404 error to my client using Windows 7 and Chrome.
When I myself user 'wget -6' from another server to retrieve the webmail I get a 404 when using https://servername/roundcube/ but using https://servername/webmail/, I get the correct... roundcube page...

So it seems there's something wrong with the access over ipv6 to /roundcube/ but I have no clue what it might be...

Any ideas on this?

I did link the ipv6 to the ipv4 and visa versa, rewrote the configs, killed firewalls etc. No cake tho...
 

sysdev

Verified User
Joined
Jul 16, 2007
Messages
379
Oh yes, the ip is not blocked. Using an ipv6 proxy I see a rc login page using the /webmail/, but the /roundcube/ returns a 404. Using ipv4, both urls return a RC login page.

From a remote server I get these responses:

# wget -6 -S https://server.com/roundcube/
--2020-10-08 14:36:59-- https://server.com/roundcube/
Resolving server.com... 2a01:a640:301:xxx
Connecting to server.com|2a01:a640:301:xxx|:443... connected.
HTTP request sent, awaiting response...
HTTP/1.1 404 Not Found
...

#
# wget -6 -S https://server.com/webmail/
--2020-10-08 14:39:40-- https://server.com/webmail/
Resolving server.com... 2a01:a640:301:xxx
Connecting to server.com|2a01:a640:301:xxx|:443... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
...

Which seems kinda stupid because /webmail/ is an alias to /var/www/html/roundcube/

Using https://2a01:a640:301:xxx/roundcube/ als fails, while https://2a01:a640:301:xxx/webmail/ succeeds.

But a client using ipv6 only gets a 404 on both... losing some hair on this :)
 

youds

Verified User
Joined
Jul 11, 2008
Messages
482
Location
Lancashire, UK
Seems like an alias is failing then. Very strange as you would expect it to work out of the box. Does seem like a legitimate bug, DA support should be able to help.

Kind regards
 

sysdev

Verified User
Joined
Jul 16, 2007
Messages
379
The funny thing is... it works out-of-the-box on ipv4. And ipv6 is nothing more than an ip in a vhost section, for apaches sake.
 

sysdev

Verified User
Joined
Jul 16, 2007
Messages
379
Bump. Still having the same issues. :(

access_log:2a01:xxx:45dd - - [15/Nov/2021:16:32:58 +0100] "GET /roundcube HTTP/1.1" 404 3590 "-" "Wget/1.19.5 (linux-gnu)"
access_log:2a01:xxx:45dd - - [15/Nov/2021:16:33:16 +0100] "GET / HTTP/1.1" 200 3644 "-" "Wget/1.19.5 (linux-gnu)"

Update:

This combination:

webmail_client=roundcube
webmail_link=webmail

Works for the ipv6 access to hostname.tld/webmail/

But it seems to break the SSO as this requires both to be set to 'roundcube'...
 
Last edited:

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
10,574
Location
LT, EU
Is ipv6 listed in /etc/httpd/conf/extra/httpd-vhosts.conf?
 

k1l0b1t

Verified User
Joined
May 10, 2020
Messages
515
Location
Belgium
Same here. Could be with the fact ipv6 is linked difirently to main ip?
Ipv4 goes into /var/www/html, ipv6 seems to go to the shared ip directory.
 

sysdev

Verified User
Joined
Jul 16, 2007
Messages
379
Same here. Could be with the fact ipv6 is linked difirently to main ip?
Ipv4 goes into /var/www/html, ipv6 seems to go to the shared ip directory.
I noticed it works on a centos 8 setup and on a little older centos 7 it failed. The newer one also does a 301 to change /roundcube to /roundcube/ (trailing slash). So the older one ends up in the wrong place somehow...

Where the failing response is a 404:

# wget -6 https://server1/roundcube
--2021-11-16 10:08:20-- https://server1/roundcube
Resolving server1 (server1)... 2a01:xxx::1201
Connecting to server1 (server1)|2a01:xxx::1201|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-11-16 10:08:20 ERROR 404: Not Found.

And the newer ons responds with a 301:

# wget -6 https://server2/roundcube
--2021-11-16 10:08:27-- https://server2/roundcube
Resolving server2 (server2)... 2a01:xxx::1301
Connecting to server2 (server2)|2a01:xxx::1301|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://server2/roundcube/ [following]
--2021-11-16 10:08:27-- https://server2/roundcube/
Reusing existing connection to [server2]:443.
HTTP request sent, awaiting response... 200 OK
 
Last edited:

sysdev

Verified User
Joined
Jul 16, 2007
Messages
379
Still no answer, but removing the ssl vhost in /etc/httpd/conf/ips.conf seems to fix it so far that roundcube on ipv6 works again...
 
Top