Vossen Posted November 1, 2016 Author Posted November 1, 2016 We switched from nginx to apache and still have the same error
SteffM Posted November 1, 2016 Posted November 1, 2016 7 hours ago, Vossen said: SOLVED. SELinux was set to maximum settings 7 hours ago, Vossen said: We switched from nginx to apache and still have the same error We can only help you if you tell us what's wrong!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.