Granted yes there probably is a "better" way. I'm not familiar with everything associated with the permissions and configuration parameters.
Is not testing this alpha/beta all about setting up interesting exercises?
If you are going to play with Alpha - and it is not Beta yet - level code then you really should know more about it. You will come unstuck fast which then diverts us from fixing things.
If you want to contribute and work on Alpha I have posted many times on how to join in.
The reality is this sort of thing helps no one.
Rightly or wrongly I'm endeavouring to build up a replica of my currently operating Server Gateway that I can swap in for short periods of time to make sure it is working as expected.
Doing that will get you in an utter mess - trying to sync the servers will be a nightmare and you are likely to lose data.
You should run it on a separate machine in a separate environment. We use generally Proxmox. Or get a cheap VPS at say digital ocean or vultr etc.
Maybe trying to run the openvpn contrib on sme11 DOESN'T work (as expected) and here is an opportunity to contribute to the fix it. I am also trying not to deviate from the stock install, where I can, to minimise variables in play.
Some packages are there but we are still too busy working on Alpha to fix them. See other posts on this. There is a time and place for this, and that isn't now.
Unless you know what you are doing then you won't be able to fix it properly and you will want us to drop everything to help you, so it isn't helping anyone.
The smeserver-openVPN contrib as I stated requires the perl-Net-OpenVPN-Manage package which is NOT currently in either ../testing/11/smecontribs/x86_64/Packages/ or ../testing/11/smecontribs-testing/x86_64/Packages/ hence the reason for querying. Enabling by including the --enablerepo=smecontribs-testing so YES I am.
Because it is probably broken and we haven't got round to fixing it it, yet. We just threw packages in the repo and left them to be fixed later. It may have old requires, or need new ones. I have no idea right now.
Note. There are a couple of us who write code, and a few who test, That's it. We have other priorities.
Likewise for smeserver-phpki-ng, all of the packages required are NOT in the ../11/smecontribs-testing directory, at least on the mirror that is being served to me, today (I just went and checked).
See above. I don't have time to fix it.
I can (and probably will) set the http-admin ValidFrom at some point to allow admin access from the LAN and maybe disable when I put in place of my current S/G. Just to make it simpler.
Bearing in mind JP is THE main man with code, I really suggest you take his advice.
Just trying to help in the effort to get SME11 up, if this is not helping that cause then I'm sorry.
I have written countless times how people can help (though very very few do). I am not going to do it again.
Random thrashing about doesn't help anyone.
Accounts on Rocket to get some assistance and guidance, discuss what you are doing, proper bug reports & verification and a mehtodical approach will.
I am not trying to be harsh - just matter of fact. In the time it took to answer this comprehensively I could have rewritten 3 or 4 templates that I am updating in smanager so you get a modern responsive manager.......
Please, follow the advice given here and elsewhere. We'd REALLY love you to help, but there is a way to do it properly to save us all time.
Thanks.