👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿👇🏿
👉🏿👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👇🏾👈🏿
👉🏿👉🏾👇🏽👇🏽👇🏽👇🏽👇🏽👇🏽👇🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👇🏼👇🏼👇🏼👇🏼👇🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👇🏻👇🏻👇🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👉🏻this👈🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👉🏼👆🏻👆🏻👆🏻👈🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👉🏽👆🏼👆🏼👆🏼👆🏼👆🏼👈🏽👈🏾👈🏿
👉🏿👉🏾👆🏽👆🏽👆🏽👆🏽👆🏽👆🏽👆🏽👈🏾👈🏿
👉🏿👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👆🏾👈🏿
👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿👆🏿
How bout this? Sync doesn’t support subscript so I’m not sure how this looks.
Filter Queen is the only US manufacturer that I know of that makes a decent canister. And also has a very simple circuit. Cord to switch to motor. Also pricey but that fucker just doesn’t quit. I know people that have had one for 20 years, and other than a slight design change in the last decade, they all mostly use identical parts.
I have no doubt that the second that FF gains a sizeable market share they will just turn in to literally every other corporation that has ever existed. They’re not special, they’re not your friend. They are selling a product to make money. And while they’re struggling, they are working their asses off to make a good product that beats the alternatives.
So until FF announced their intention to DC, I’m not telling a fucking soul.
I figured out the problem, digital ocean was only applying the top RSA key, which is my Putty key. The keys I added to DO via WSL were not getting added to the authorized key list. So I added my key to the authorized keys file and it worked. Well, it let ansible access the server. I’m having other issues but will work on them later.
Apparently including the people who developed Lemmy who chose to recommend Ubuntu…
It doesn’t tell you to actually run nginx
That may be so, but the link that they give references a digital ocean guide that DOES (it’s literally step 2). So, am I just ignoring that part? How do I figure out which parts of a guide should be followed and which ones shouldn’t?
running nginx isn’t complex enough to warrant a guide
I haven’t gotten it to work yet so I disagree.
I can’t even get that far.
I used a different PC, installed WSL, created a new rsa key stored at “/home/wsl/.ssh”. Added the public key to my DO droplet. Rebuilt the droplet to ensure that the keys transferred.
ssh -i /home/wsl/.ssh/id-rsa root@ip
Permission denied (public key)
every 👏 fucking 👏 time 👏
I would love to try the ansible method, but apparently I’m the only person to not just instinctively know how to ssh from another pc. I’ve searched for a reference to this and none of them help. Any advice?
Oh okay, that makes sense. Thanks for the perspective!
Thanks for the link. I tried it out and had a problem with the “lemmy.hjson” file. It doesn’t look like I would expect, there is a bunch of non-sense. I did the wget command again and checked “config.hjson” and it is identical. So I think there is something wrong with that file.
Yes, it worked, but as I’ve told others, the dev did not make it for a production use case. They said they intended it to be used by “people in college that are just testing”. Several features don’t work and are not going to be supported, like SMTP, which I will require. They also said they didn’t intend to have more than one user of the instance… No idea who this usecase is for…
Oh, so my router, 🤣 lol, my bad.
And yes, I use Putty to access the server currently. root@IP with an RSA key. It works perfectly on Putty. Ansible just will not connect. No idea what to do there. It just says “UNREACHABLE”. I have added and removed a dozen or so keys generated on the WSL Ubuntu Ansible local machine and none of them work.
It’s going to sound unhelpful, but have you tried running the Ansible stuff from WSL? This is tested on Linux (and macOS probably), but probably not Windows. That’s exactly what I’m using, WSL Ubuntu.
And I’ve tried Lemmy-Easy-Deploy, and it worked fine, but the developer told me that they didn’t intend for this to be used for an actual deployment instance with many users. I plan to scale this as large as I need. They also said that it did not support SMTP and that they had no intention of supporting SMTP. But without SMTP, users won’t be able to confirm emails or reset passwords… So it just won’t work.
Please post full logs of what you’re running, it will be easier for people to troubleshoot, including everything before. The extra context can be very helpful to know what Ansible did before and give clues as to what it did previously that might fail. That stuff is a moving target, it gets updated frequently and may fail under some unanticipated conditions.
Good point. I can do that. I have made so many impromptu modifications to my current server that troubleshooting it any further would surely cause errors. So I will blow up the droplet, start fresh, and get it to the first error and post back. Thanks for the advice!
No problem at all. Thanks for getting back to me. I really do appreciate it!!! I have a busy day today too but I’ll try to be vigilant about responding.
I am using digital ocean.
Have you setup your ISP router to route ports 80 and 443 to your server?
I don’t know what that is. What is an ISP router? Is that a config file on my server? You really need to spell it out. I am following the guides. That is what I know. If you have a better guide that uses this verbiage then please send it. I am happy to learn.
And during the docker method, I was trying to set up nginx and the status is inactive. It will not start.
Here is the status message:
Starting A high performance web server and a reverse proxy server...
nginx[29280]: nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/my_domain_name/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system>
nginx[29280]: nginx: configuration file /etc/nginx/nginx.conf test failed
systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
systemd[1]: nginx.service: Failed with result 'exit-code'.
systemd[1]: Failed to start A high performance web server and a reverse proxy server.
but they assume you have some experience doing this stuff
I can appreciate that, but I don’t. So, if you are saying that I should just quit because I’m not an experience web developer, then thanks, and no thanks.
For the better part of the last two decades, once or twice a year I throw a linux distro on a computer to see how it is. And of those several dozen times, EVERY SINGLE TIME, I have encountered an issue that needed troubleshooting and was never resolved. And every single time, I have found myself being advised that “you just have to know how to do this already”. So I get what you are saying, but I don’t. I don’t have experience with this because it always ends up like this. I fucking hate windows, but it works. I can google a problem and find a solution within minutes. Literally any problem has a solution. Not so with linux. Just a lot of people telling me I just need to “know more”.
Okay, so it looks like nginx is a reverse proxy. That is the step I was on. It doesn’t work. Last thing I did was to modify the docker-compose.yml file and change the port from 80 to 1236. I was told to do that by someone who has been trying to troubleshoot with me for 2 weeks now. It doesn’t say to do that anywhere, but they told me to so I did. Then they said to “add this to my upstream” but I haven’t a fucking clue what that means so I don’t know what to do next. There is a config file in etc/nginx/sites-enabled/nginx.conf that the guide directed me to edit. This is the guide that I was directed to use to set up nginx. I was on the step where it requests the nginx status and mine just says “inactive”. I promise, I am following these guides PRECISELY. I don’t know what I am doing wrong, but all the solutions that I have received are things that the guide DOES NOT say to do. So I don’t know where I am. I am happy to start fresh. You just let me know.
Okay, I keep getting this question re: “reverse proxys”, but I’m having trouble answering this because the guide does not use that language. There are no steps that direct me to edit, add, modify a “reverse proxy”. So if there is a step in the guide that you know to be a “reverse proxy” then please tell me what it is. I am following the guides EXACTLY. There are a lot of missing steps, but most of these are things that were implied by the guide and not explicitly stated.
I have tried the docker method. I have gotten close with this, as in, I can use the IP to access the instance, but I have not been able to get the domain to work. My A record is set up correctly. I used lemmy-easy-deploy to get it working the first time and it DID, but that dev does not support instances made for actual deployment so many features just don’t work. It’s not feasible at all. But my domain DID work. So I know my A record is set up correctly.
I have tried the scratch method. That was a nightmare and nothing worked as expected. I am more than happy to try if you are willing to help me negotiate it.
I have tried the ansible method. My local PC will not connect to the server with ansible. I have created a dozen new keys and NONE of them work. Ansible WILL NOT CONNECT. I have been using Putty to access the server and it works flawlessly, all day, every day. So I obviously have a working key. Ansible is not working. It just keeps saying “UNREACHABLE”. I have googled this and found no solution that even remotely addressed what I am trying to do.
I don’t know what to do so you tell me and I’ll fucking do it. Would you like me to start with the docker method? Would you like me to try the ansible method? Would you like me to try the scratch method? You tell me. I don’t know. I don’t care. I just want to get it working.
I am willing to try any method you prefer. I’ve failed at all of them and have no preference. I don’t care how I get it working, I just need to see something work. Please, please, please help!!!
Yeah, that’s what it did on sync. But it looks legit in FF.