Re: [users@httpd] apache 2.4 and automx configuration

2018-03-30 Thread David Mehler
Hello, Thanks. By adding gibberish inside the IfModule section I found out that it was not working. I then commented the IfModule stuff out so the code loads unconditionally. Now I'm getting a 500 internal server error. If anyone has automx going with apache please let me know. The error seems to

Re: [users@httpd] apache 2.4 and automx configuration

2018-03-30 Thread Eric Covener
It seems like if mod_uwsgi was not loaded or that was otherwise in error, your document root would reject all access because all of the "require all granted" are wrapped in the IfModule. I suggest verifying that the module is loaded and your specific syntax for the IfModule works as expected (by

Re: [users@httpd] apache 2.4 and automx configuration

2018-03-30 Thread David Mehler
Hi, Has anyone checked out my last message? I was wondering if anything stood out with this config? Thanks. Dave. On 3/30/18, David Mehler wrote: > Hello, > > Sorry been going between three projects and must have been hitting the > enter key to fast. Here's the configuration. > > Thanks. > Dav

Re: [users@httpd] apache 2.4 and automx configuration

2018-03-30 Thread David Mehler
Hello, Sorry been going between three projects and must have been hitting the enter key to fast. Here's the configuration. Thanks. Dave. #cat provisioning.example.com.conf # The autoconfig.example.com and autodiscover.example.com http virtual host ServerName autoconfig.example.com #Serv

Re: [users@httpd] apache 2.4 and automx configuration

2018-03-30 Thread Eric Covener
> Can anyone spot any obvious errors with the below apache > configuration? You didn't include any apache configuration in your mail. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: u

[users@httpd] apache 2.4 and automx configuration

2018-03-30 Thread David Mehler
Hello, I'm trying to troubleshoot an automx error that it's giving me a 403 message, I'm using FreeBSD 11.1, and apache 2.4, and of course automx. It's looking not like an automx-specific issue, but an apache-specific issue. Can anyone spot any obvious errors with the below apache configuration?