SoftEther VPN should be updated:
I’am tempted to remove it from dietpi-software. There are far too many steps for the end user that cannot be automated.
OpenVPN really is so much simpler for the end user, and, it automates really well as an install.
If nobody is using it, except me, then you can remove it 
hehe, wasn’t it you who requested OpenVPN for DietPi-Software
Yeah it was lol:
https://dietpi.com/forum/t/request-openvpn-server/97/1 
SoftEther provides more things, like L2TP.
I couldn’t manage to run OpenVPN on port 443.
Could you please return SoftEther VPN option? OpenVPN is slow and ugly, moreover that it is impossible to use without forwarded ports. SoftEther is the only VPN that works behind NAT, and its support was the very reason I migrated to DietPI. Please-please-please consider restoring it!
Hi Starlight,
Unfortunately, SoftEther VPN will not be returning to DietPi for the moment.
Implementing and supporting Softether VPN is too time consuming and I have limited time I can devote to DietPi as it is.
The other reason is due to its end-user setup with the client software. Its over complicated and we can’t automate that side for the user.
You can however install SoftEther VPN server manually on any DietPi system. This guide may be helpful.
Here is the DietPi source code for installing SoftEther VPN server, before it was removed.
Install code: https://github.com/Fourdee/DietPi/blob/2b3c38f0182a12085347153bb979b3030e0fd70d/dietpi/dietpi-software#L846-L886
Config code: https://github.com/Fourdee/DietPi/blob/2b3c38f0182a12085347153bb979b3030e0fd70d/dietpi/dietpi-software#L2551-L2563
@FourDee thank you for detailed explanation! Also, thank you very much for introducing hassle-free wifi hotspot solution, it is much appreciated.
For several years I have run OpenVPN servers in bridge mode on several Linux distros.
While OpenVPN clients could easily connect to the OpenVPN server from behind “SOHO” routers,
I have found it to be impossible from behind a more strict firewall,
even if the OpenVPN server was listening on port 443.
That’s because these firewalls not only block every port, except 80 and 443,
but they also inspect the IP datagram to see if the protocol is in fact HTTP.
And OpenVPN is not using HTTP, so: no client-connect…
Thanks to your Diet-Pi distribution, and your SoftetherVPN installer,
I was finally able to connect from behind an “Industrial-Grade” firewall.
That’s because SoftetherVPN uses the HTTP protocol to masquerade its VPN payload.
Now the OpenVPN Linux box is power-off,
and the Raspberry-Pi with your Diet-Pi and your SoftetherVPN is online.
As for the client-side customization:
I found the administration GUI from the Softether project very easy. °
(while on the LAN)
And the client GUI from the Softether project is also much better than the OpenVPN GUI. °
(while on the WAN)
° (I used both downloads for MS Windows)
No command-line utility had to be used.
https://www.softether.org/
I appreciate your previous work on this project, and the link to the previous install method.
Perhaps the Diet-Pi community may see a revival of SoftetherVPN,
when new OpenVPN users encounter the same problems that I previously had…
Grtz from FC.