BUG Report 2.2.30 - Co-Domains

New version stable 2.2.30 has a bug concerning Co-Domains.

I have created Co-Domains for users to access subdomains such as:

admin.domain.org (forward tab: https://www.domain.org:81)
webmail.domain.org (forward tab: https://www.domain.org:81/roundcubemail)
mailuser.domain.org (forward tab: https://www.domain.org:81/mailuser)

After 2.2.30 none of them work, they all omit :81 and forward to:

https://www.domain.org

with or without the slash.....

I only have about 30 domains on my personal box....but my bosses servers have over 2000 domains configured this way.

The only possible solution I can think of is to create a domain webmail.domain.com with it's on webspace which is unnecissary and ridiculous with an apache redirect to the webmail/admin/mailuser pages....but to do this for over 2,000 domains!!!

Has anyone had this problem?....or is anyone smart enough to fix it?

Thanks guys

-k

 

Please have a look here: http://www.howtoforge.com/forums/showpost.php?p=176629&postcount=18, it might help.

Persnonally, i think there is a bug indeed. I can add co-domains more then once with the same name.

 

@Till,
I just upgraded one system with the SVN version and the problem with co-domains seems to be solved now.

 

thanks

Hey thanks,

Before I install...exactly how did u fix the problem?

Any path, file or variables or line #'s heh or whatever would be helpful.

Thanks again, I'll diff it

..oh wait just checked out ur link....u guys rock...gonna continue with u guys on my own servers.

But still no luck....no luck going to Co-Domains webmail.domain.com

forward to https://www.domain.com:81/roundcubemail

forwards to https://www.domain.com/roundcubemail



thanks guys

 

OpenSSL bug

Maybe it could be an openssl bug?

Because I just tried to submit an ISPConfig generated SSL Certificate to my RapidSSL provider and it said that the SSL certificate was to long

same error i get on all my co-domains......

ISPConfig 2.2.30
Debian Etch 4.0

 

SSL Cert

Possibly, Thanks for the suggestion I will check that!

It may be because I just bought a rapidSSL thing and when i tried to enter it in there it said too long.

Also, I tried the:

Code:

$domain["domain_weiterleitung"] .= strtolower($domain_weiterleitung_url_parts['host']);

That Falko provided for me and I still got the error:

Error code: ssl_error_rx_record_too_long

However this error just started showing up when I upgraded to 2.2.30. I'd been using the same cert since 2.2.18 and never changed it...and it gave me the same error above after the upgrade.

 

Thank You Falko

Actually I must have had an extra character or something in the config file because falko's solution worked.

Thank you falko and till...lets not forget Hans the man...that guy is cool *bows down*

respekt to u

If I ever get out that way we should have a drink....i have my other areas of computer expertise, low level ASM and stuf like that but not much...take care and thanks again guys

Because of you guys I got a better job! ...hehe go figure...much pr0pz

Long Live The ISPConfig Krew! ... .. . ... . ... . . . . . b0h! b0h!



Take care

 

Any idea when 2.2.31 will be released? I want to fix teh problem but do not want to stay with the official releases

 

It was released today: http://www.ispconfig.org/news.htm

 

I never saw this

I never saw this bug

can you please post the direct link since this forum post is old so i can read about it.

Thanks