If that doesn’t help, you should maybe completely remove your apache2 configuration, disable the Apache repo, install the standard apache packages that come with openSUSE, and see if it works then without changing anything (especially not in YaST).
As I said, it should work fine out of the box with the default configuration.
You can still make changes to the config afterwards when you’re sure that it’s working.
And then it shouldn’t be hard to revert a config change if you find it not working.
I don’t think so.
The point is to get a new default configuration.
/srv/www/ doesn’t contain any configuration.
It might be a good idea though to check whether there’s any .htaccess file in the path, as this can of course also change the config and/or prevent access to specific directories. Maybe do that before you try to remove the config and reinstall apache:
On 2014-06-26 20:56, wolfi323 wrote:
>
> robin_listas;2650891 Wrote:
>> I would also remove the /srv/www directory, or part of it, no?
>>
>
> I don’t think so.
> The point is to get a new default configuration.
> /srv/www/ doesn’t contain any configuration.
No, but files with wrong permissions, perhaps. Or on the wrong tree. If
the point is an install from scratch… :-?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
User “wwwrun” should have access to /srv/www/htdocs/ (especially /srv/www/htdocs/index.html) and all directories in that tree.
The point for me is not really an install from scratch, but to switch back to the “official” openSUSE 13.1 apache packages with their default configuration. Because I am sure that they work.
I haven’t tried apache 2.4.9 from OBS, and I don’t know whether the YaST HTTP-Server module (which the OP apparently used to configure Apache) fully works with Apache 2.4.
I remember having read some mailing list posts where YaST created a configuration that didn’t work with 2.4. No idea whether this has been fixed yet.
Well, I looked at the whole thread again, and have spotted the problem now:
The ‘x’ bit is missing for the owner, i.e. user wwwrun (Apache).
How could I possibly overlook this the first time? Maybe because he didn’t use CODE tags… :sarcastic:
So @Dexter22, just run this and the error should be gone: