SSL Cert Common Name mismatch for sub domains

Yes, it is.
Just FYI: This Server has multiple sub-domains, all pointing to the same IP.

 

Ok, you´re possibly pointing me to the right direction.
This sub domain is used for a seafile installation and therefore has some special Apache directives which may be the root cause.
But this sould be a common case and not blocking LE certs.
Pls. find the Apache snippet attached.

 

Ok, good idea, just to avoid errors from this side: AAAA record (temporarily) disabled.

 

Ok, now the solution (google´s your best friend):
Add this line to the Apache directives:
ProxyPass /.well-known/acme-challenge !

Thks. to all for your help.

 

Problem solved, add this line to the Apache directives (at the top) and anything goes fine.
ProxyPass /.well-known/acme-challenge !

 

how about native support for domains behind a proxy? nodejs and for docker for sure? Probably already in youe mind? @till
stuff like this could be handled by ispconfig
or maybe more correct, domains in front of a proxy ^^

 

I can't seem to find an easy entry on website setting where I could say
[x] rewrite requests to backend which is:
[_________]

is it via ip mapping?

Edit, nevermind, I found it on redirects ... too bad it only works for one path / allows for one setting only

 

yeah I was editing my post while you added this thanks, is still limited though :/
I had an old setup where I redirected some tools like /pma/ /grafana/ /elk/ /monit/srv1/ things like that.
for nodejes and docker I'd expect more need of such

 

sure, but those are not valid alternatives in the sense of making ispconfig better.
snippets imho should be just that, snippets you'd share with other clients or do some common tasks.
specific backends for a domain are not such a thing.
I'd prefer a redirects tab where multiple (proxy)-redirects could be easily entered, enabled, disabled. I think that'd be a quality of life feature.

I'm not asking for it, but I think it'd be nice.

 

plesk - and others - offer a simple and advanced view. simple view could be what it is now, advanced would unlockthe foreach?
Well the most complaints I receive, whenever I try to make people use ISPConfig, is the UI.
Maybe autohide some features which depend on things not enabled might make a cleaner view of things, or just some better categories.

Working with the ispconfig api right now, thank you for json by the way, and yeah... it really is a patchwork and could use some heavy redesignsat some points. Though I think I can estimate the cost of such a thing and have to admit, probably nothing for the near future ^^

 

maybe just needs some redesign then. Plesk has tons of bloat and somehow it is loved still and they hide it somewhat neat at some places. It's still a pain to have such setups in the fleet ^^

yep, I can relate to that feeling, unfortunally. And worse.

Well 7 years ... 3 years to go, then you can say not even RedHat gives support that long =) *cheer*