Conversation
Notices
-
So, no. I do not have goddamned nginx figured out, and no, the Pleroma 2.0 launch has not made this any less goddamned infuriating.
Sunday, 15-Mar-20 04:19:48 UTC from web-
@scribus Can you point me to the directions you're using? I could try it.
-
@thismightbeauser https://docs-develop.pleroma.social/backend/installation/debian_based_en/#nginx Literally the official how-to, presumably by the people themselves. I think what's actually hanging me up is the Nginx .conf files, but I got it to work for Wordpress and I can't figure out why Pleroma is so godrotten different. I know "Copy the example nginx configuration and activate it:" has been a dealbreaker step, because the filename format isn't at all what it should be for the *.conf files (at least, so far; I've used sub.domain.tld.conf just fine, until the social.* one I'm trying to add)
-
@scribus Can you give me your `lsb-release -a` and your `nginx -v` also? Thx.
-
@thismightbeauser So run those commands at the command line at lmk what the result is.
-
@scribus Told you, ask rin, he's handling that stuff.
-
@thismightbeauser Hey, sorry I didn't get back to you. Just been sick of life. Nuked the sever, anyway. Didn't need to keep paying for something that wasn't working anytime soon. Maybe I'll be taking another stab soon, on the back of this stimulus check. Thanks.
-
@scribus That's okay. I feel that, especially with the way the world has been lately.
-
@scribus Can I ask what you were having trouble with when using NGINX?
-
@oracle It was the config file settings specifically for Pleroma. I got Wordpress to work, and I got subdomains to work, but the exact path or whatever to Pleroma evades me. Where you'd normally tell it the site is at /dev/www/site or whatever; I cannot for my literal life figure that out for Pleroma. It installs, Nginx installs, the two do not play together.
-
@scribus The installation of Pleroma comes with an NGINX config file located at /opt/pleroma/installation/pleroma.nginx copy it to the NGINX sites-available directory, change your server names, then symbolically link it to the sites-enabled path
-
@oracle I had done that previously and it still wasn't working. The directions said to name it a certain thing, which was not the usual Nginx method of naming it the same as the URL is supposed to be. Might that have been my problem? The second time around, I did try modifying a default, instead of copying the provided one, so obviously that was the error, there. :p Thanks.
-
@thismightbeauser Well, my latest (balls-deep-in-failure) attempt is on Ubuntu 20.04, and nginx is 1.17.10 (Ubuntu)
-
