SharkWipf

After reinstalling, reconfiguring and even going through the trouble of enabling ssl on my webserver, I've finally found and fixed it. I decided to watch my server logs when trying to create a new modpack. I noticed a 500 error at /api/modpack. While visiting that page myself, it turned out that database caching didn't work. After switching back to flat file caching, everything worked right again. Still, the fact that the technicpack.net server throws a PHP error on an API, albeit misconfigured, can't be intended behaviour, right?

Regarding the error on trying to create a modpack, it indeed seems to be related to the Solder-linking. I don't get the error on a non-linked account. I can't get the Solder-made modpack to show up under "My Modpacks" either, though I am not sure if it should. This is the error I get: [EDIT] Oops, sorry for the doublepost

Oooooh, I see. This way of packaging makes a lot more sense now. Thanks!

I am playing a bit with the Solder API as well, I can't seem to find a way to ship default config files or coremods though. Am I missing something here? Also, does the "Create a modpack" option on technicpack.net give an error for everyone atm? Or is that because I linked to Solder, and something is wrong with my install (it looks like a technicpack.net-sided error though)?