"Hmm, I need Pleroma to show up at http://pleroma.mercurial.blog";
"Oh, I'll just make Pleroma run at port 80"
Q3XulC7U0pVs2A.png

cc @MercurialBlack

@meso Thus far it's worked besides random freezes

@meso You see I know nothing about networking I don't understand the negative implications of this

@MercurialBlack you cant host anything else on port 80 or on subdomains. you need a web server like nginx to proxy say whatever's running on port 9000 to say pleroma.mercurial.blog:80. this way you can proxy whatever's running on 8080 to bloat.mercurial.blog:80

@meso If you're wondering how I got both pleroma.mercurial.blog and mercurial.blog working, they point to separate IPs.

@MercurialBlack give me access to your server Now

@meso It's two servers technically also no

@meso I'm guessing I shouldn't have anything directly on 443 either?

@MercurialBlack Please king install cady

@MercurialBlack caddy

@meso See you on the other side o7

@meso I'm still here which means I've fucked up fuck

How do I deal with 443 I think pleroma is using both 443 and 80 even though it lies and says it only uses http

@MercurialBlack This racial slu so retarded i swear to God

@meso in pleroma.conf I have two servers one for 80 and one for 443

@meso K I looked it up someone says it's only supposed to run on the 80 one so what's the point of this block

@MercurialBlack are you using caddy or nginx

@meso both