search

spritsail / amp-minecraft

Dockerfile for running a Minecraft server through the server management program AMP.
6 stars 2 forks source link

Neither SMTP nor Pushbullet work #3

Open shawly opened 5 years ago

shawly commented 5 years ago

See this: https://github.com/CubeCoders/AMP/issues/47

There seems to be an issue with the SSL certificates used in the container.

frebib commented 5 years ago

I've seen this before with MonoBtls actually. Does this happen before restarting/recreating the container? Certificates are handled in a non-standard and weird way which makes it a pain, but afaik they're in the correct format and location.

I'll try to find a few hours to sit down and debug this over the weekend, although at this point I honestly advise not using this container because it tries to work around so many AMP assumptions and design flaws.

frebib commented 5 years ago

We do call ampinstmgr to sync the certs before starting which is all that should be required. https://github.com/spritsail/amp/blob/master/start.sh#L10

I wouldn't be surprised if that didn't work though

shawly commented 5 years ago

The issue appears as soon as the container is started and tries to connect to anything via SSL.

If it actually isn't able to sync the certs it would explain why SMTP over SSL and Pushbullet won't work, but SSL over port 25 works fine, but I don't wanna use SMTP without SSL or TLS. I've also seen that at the start of the container it also says it couldn't get any version information on Spigot, because it tries to get the list of versions from an SSL connection and downloading plugins also is an issue depending on where it wants to download them, EssentialsX for example produces an error when downloading and I assume it also tries to download it over HTTPS, while some other plugins do work like MultiverseCore. But since the plugin manager of AMP provides a lot of outdated plugins from spigotmc.org I don't use it anyways.

I'd like to provide more info, but since the logging of AMP is not really verbose in any way and does, from what I can see, not provide any option to turn on debug logging, it's kind of a problem.. I really want to continue using your container since it works great besides the SSL issue which still seems like an AMP issue to me.

What I really don't want to do is use AMP to manage my Docker instances, this feature is in my opinion pretty nonsensical in it's current implementation.

frebib commented 5 years ago

I have had multiple heated discussions with the AMP devs/users about their abuse of the Linux implementation- I don't think it will ever improve. If you want my opinion, stop using AMP and use/write something better.

Having said that, this isn't the first time I've seen SSL issues with AMP, both before and after the Btls change. If you give me a rough container startup config and instructions I can try to reproduce and debug from there.

I agree with not having to use ampinstmgr. It's an overengineered bash script at best that makes poor assumptions and distro-specific hacks- we shouldn't use it.

shawly commented 5 years ago

Here's my compose file: https://github.com/shawly/docker-templates/blob/master/amp/docker-compose.yml

But you can save the trouble of finding where the problem is, since AMP, it's devs and their attitudes are definitely the issue here. I started looking at some other interfaces which I can run in a small alpine based container, preferably open source. Since I got a McMyAdmin 2 license, I could still run McMA2. But it's seemingly uninterested devs and the poor documentation are forcing me to stop using their products.

I think I'll go with Pterodactyl or Pufferpanel!

Thanks a lot for your time and help!