Post AJfd6TZPyRPRqo8daC by Prude@beefyboys.club
(DIR) More posts by Prude@beefyboys.club
(DIR) Post #AJfd6TZPyRPRqo8daC by Prude@beefyboys.club
2022-05-21T07:54:00.147256Z
3 likes, 3 repeats
About an hour until I take this instance down probably forever, to live on only as a dumped database. I encourage anyone seeing this to refollow our people on Beefyboys.win if you haven't. It was fun fucking up a bunch and learning about the fedi and the basics of working on servers since last May via this first instance. ❤️
(DIR) Post #AJfdU5vhWL7JTrp6ZM by mint@ryona.agency
2022-05-21T07:58:08.017591Z
0 likes, 0 repeats
@Prude @Prude Can you at least copy all media to bb.w and set up the global bb.c -> bb.w redirect? So that images won't break on instances that have remote posts before closure.
(DIR) Post #AJfdixTZEYRtbbkeiu by Prude@beefyboys.win
2022-05-21T08:00:58.562345Z
1 likes, 0 repeats
Yeah I can try to figure out how to do that, won't discontinue the VPS immediately anyhow since there's some other stuff I wanted to do behind the scenes. I was at the least going to have the BB.C domain redirect to BB.W for the remainder of its term (which should be until next May). What you're suggesting sounds a bit more involved than just doing that and merging the uploads folder, but I can see about implementing it or if you have any tips/guides, I'll use them.
(DIR) Post #AJfellALYgV2FXf2bQ by mint@ryona.agency
2022-05-21T08:12:31.340328Z
1 likes, 0 repeats
@Prude @Prude I think what can be done is the following:>point bb.c to bb.w server>copy over the /media folder from bb.c to bb.w>set up nginx host for bb.c with similar configurationserver { server_name beefyboys.club; location / { return 301 https://beefyboys.win$request_uri; } location ~ ^/(api|users|objects|notice|.well-known) { return 410; } location /media { root /path/to/folder/with/media/folder/not/media/folder/itself; }}
(DIR) Post #AJfeunon4Bap58tFOC by Prude@beefyboys.win
2022-05-21T08:14:19.368829Z
0 likes, 0 repeats
Great, I'll try that!
(DIR) Post #AJgFBpz1rmah4O6LTM by Prude@beefyboys.win
2022-05-21T15:00:45.206391Z
0 likes, 0 repeats
Implemented it, seems a little fucky--about 50/50 on media items that are loading alright and those that aren't. Dunno what the confounding variable would be there for the discrepancy, but whatever, it's not super critical to me.
(DIR) Post #AJgG4bkwSrAMs7d2zw by mint@ryona.agency
2022-05-21T15:10:31.287264Z
0 likes, 0 repeats
@Prude @Prude You forgot the cert, trying to access it over HTTPS returns cert error, and when ignored, it just opens the same bb.w.>Firefox does not trust this site because it uses a certificate that is not valid for beefyboys.club. The certificate is only valid for beefyboys.win.>Error code: SSL_ERROR_BAD_CERT_DOMAINWith plain HTTP, redirect and 410 Gone on API points seem to work fine, but all media I've tried returns 404. Make sure the path to folder is right.
(DIR) Post #AJgGGHzVmB0b2y0uDw by Prude@beefyboys.win
2022-05-21T15:12:46.500286Z
0 likes, 0 repeats
Ah, it would definitely be strange on the media loading atm since I was tinkering with some stuff after posting. If it needs to be HTTPS, I assume getting a cert for it would be just like getting letsencrypt set up for the live instance?
(DIR) Post #AJgGRYbaLUCflBCATY by mint@ryona.agency
2022-05-21T15:14:38.236794Z
0 likes, 0 repeats
@Prude @Prude Yeah, same as you did it for the rest of servers.
(DIR) Post #AJgHmGLFXm6X9UzWxU by Prude@beefyboys.win
2022-05-21T15:29:46.330266Z
0 likes, 0 repeats
Okay I generated a cert for it and set up webroot renewal+cron, this is what the config for that section looks like at this point. Regarding file location, I have this pointed at /beefyboysclub/media while my upload files themselves were dumped in /beefyboysclub/media/media since I understood the instructions to be that your root media folder is supposed to be one up from where the files are actually contained?
(DIR) Post #AJgI3CufXqKPRPddwW by mint@ryona.agency
2022-05-21T15:32:40.068766Z
0 likes, 0 repeats
@Prude @Prude 1. Try to change "location /media" to "location /media/". That might be a fuckup on my side, sorry, as nginx might be interpreting it as a file named "media" instead of directory.2. Don't forget to make it listen on 443 the same way you've done it on bb.w.
(DIR) Post #AJgIPviJeoeMl7hAo4 by Prude@beefyboys.win
2022-05-21T15:36:54.869902Z
0 likes, 0 repeats
Added the tailing slash for media location. I suppose regarding 443, you mean making a version of the SSL session section for BB.C too? I'll do that now.
(DIR) Post #AJgIW8RdEl43yrqmki by mint@ryona.agency
2022-05-21T15:37:53.394320Z
0 likes, 0 repeats
@Prude @Prude >you mean making a version of the SSL session section for BB.C tooYeah, since bb.c operated with HTTPS when it was live, meaning all links in other instances' objects are with https as well.
(DIR) Post #AJgIdhpy2yCbm9qLIW by Prude@beefyboys.win
2022-05-21T15:39:25.876724Z
0 likes, 0 repeats
That makes sense
(DIR) Post #AJgJtEYolRifYzn1Rg by Prude@beefyboys.win
2022-05-21T15:53:26.562465Z
0 likes, 0 repeats
Alright I got that section set up too now, will do some testing
(DIR) Post #AJgKGdLskyWz73tgES by mint@ryona.agency
2022-05-21T15:57:30.475002Z
0 likes, 0 repeats
@Prude @Prude It points to bb.c again, but this time with valid bb.w certificate. Just make the server block with all the same strings except listen ones, and add listen/ssl_* strings from current config.
(DIR) Post #AJgLYs7MhDyc4iMpo8 by Prude@beefyboys.win
2022-05-21T16:12:10.415774Z
0 likes, 0 repeats
This part lost me a bit. For now I have two basic server blocks (one for each site), both listening on 80, and two SSL blocks, both listening on 443. Are you saying to drop the port 80 listen for BB.C and have it listen on 443 on its basic server block too?
(DIR) Post #AJgLm5yAVVqkneN4Jk by mint@ryona.agency
2022-05-21T16:14:23.836765Z
0 likes, 0 repeats
@Prude @Prude :boomer:Let's rephrase it. Go to SSL block for bb.c and remove everything except listen and ssl_* directives. Then copy everything from bb.c port 80 block, except its listen, and paste it into cleared SSL block.
(DIR) Post #AJgLndeIlz03XpoYgC by Prude@beefyboys.win
2022-05-21T16:14:50.564195Z
0 likes, 0 repeats
I see, alright
(DIR) Post #AJgMbfYtw1plxN92vY by Prude@beefyboys.win
2022-05-21T16:23:52.971004Z
0 likes, 0 repeats
So now I'm looking at something like this:
(DIR) Post #AJgMebdoy5uWfKqXrc by mint@ryona.agency
2022-05-21T16:24:14.656741Z
1 likes, 0 repeats
@Prude @Prude Should be fine.
(DIR) Post #AJgMqp134FHpcaXHfM by Prude@beefyboys.win
2022-05-21T16:26:37.513959Z
1 likes, 0 repeats
Oh yeah, I navigated to my old profile from here and now 100% of it is displaying. You've been a big help, and this actually helps my confidence in figuring out alternative frontends on subdomains when I get around to it. Thanks! 🙏
(DIR) Post #AJgMz8b09b38fEJlho by mint@ryona.agency
2022-05-21T16:27:58.045747Z
0 likes, 0 repeats
@Prude @Prude No problem, glad to be of help. Your config still is a bit of mess that could be organized with include directives and similar stuff, but as long as it works, it's fine.
(DIR) Post #AJgNMR4LdWWWcP9avQ by Prude@beefyboys.win
2022-05-21T16:32:20.305158Z
0 likes, 0 repeats
Yeah, I basically have only ever used the default nginx config provided upon setup of these instances, with the necessary modifications to point it at one's domain, enabling webroot renewal, and adjusting the upload size and stuff being the most I've done. Definitely have more to learn there. 🙃