I found that this talk (selinux for mere mortals) was good for me to start off - <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=cNoVgDqqJmM" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=cNoVgDqqJmM</a><p>After that, Red Hat&#x27;s documentation was probably the next most useful thing for getting started; <a href="https:&#x2F;&#x2F;access.redhat.com&#x2F;documentation&#x2F;en-US&#x2F;Red_Hat_Enterprise_Linux&#x2F;7&#x2F;html&#x2F;SELinux_Users_and_Administrators_Guide&#x2F;" rel="nofollow">https:&#x2F;&#x2F;access.redhat.com&#x2F;documentation&#x2F;en-US&#x2F;Red_Hat_Enterp...</a><p>But mostly it was a lot of proding and poking whilst setting various things up that helped a lot, and remembering that when something doesn&#x27;t work, to check selinux first.<p>The &#x27;settroubleshoot-server&#x27; package for the Red Hat based distributions is also good whilst you&#x27;re getting started in dev, as it takes the avc logs and &#x27;guesses&#x27; what the likely cause of the problems you&#x27;ve had are, giving percentage likelihoods of the policies and booleans that might be causing problems.