- 6 Posts
- 16 Comments
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[SOLVED] Need some guidance with upgradingEnglish1·2 years agoMeaning I just wait a bit and retry later?
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[SOLVED] Need some guidance with upgradingEnglish1·2 years agoUpgraded to 0.18.5, which now gives me this error:
lemmy-lemmy-ui-1 | API error: FetchError: request to http://lemmy:8536/api/v3/site?auth=AUTH_KEY failed, reason: connect ECONNREFUSED IP_ADDRESS:8536
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[SOLVED] Need some guidance with upgradingEnglish1·2 years agoI created a gist with my compose file: https://gist.github.com/osiriswrecks/26a875576d3bbcf11923d7715ac15e6e. It should be stripped of all private info. I tried changing the version from 0.17.3 to 0.18.0 and the server returns a gateway error after restarting.
penguin_ex_machina@lemmy.worldto Linux@lemmy.ml•Red Hat refuses Alma's CVE patches to CentOS Stream; says "no customer demand"352·2 years agoIt’s a bold strategy, Cotton. Let’s see if it pays off for them.
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[Solved] Instance keeps returning "no_email_setup" errorEnglish0·2 years agoDone. And restarting the lemmy container appears to have helped! Now if I click “forgot password” with my email in the user field it at least shows a “sent a reset email” notification. I don’t see an email yet though, either in inbox or spam, and no error logs from what I can tell but I’ll keep looking.
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[Solved] Instance keeps returning "no_email_setup" errorEnglish1·2 years agoAh SHIT. Thanks, doing it now.
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[Solved] Instance keeps returning "no_email_setup" errorEnglish0·2 years agoI updated my
docker-compose.yml
above to the full file. Does that help?
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[Solved] Search bar on personal instance only returns local resultsEnglish3·2 years ago!!! THAT DID IT.
Thank you so much I would have never gotten to that solution on my own. Works beautifully now.
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[Solved] Search bar on personal instance only returns local resultsEnglish2·2 years agoI’m almost positive that network is already there but I’m definitely going to check the Lemmy-specific logs. I only knew how to check the general server logs when I last looked at it. If I ever get my kid to bed I’ll take another look.
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[Solved] Search bar on personal instance only returns local resultsEnglish1·2 years ago“No results” never goes away though. I’ve straight up left it and walked away for like 10 min and no change. That’s why I’m starting to wonder if it’s an issue with my instance.
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[SOLVED] How to configure Lemmy instance nginx proxy for websockets?English1·2 years agoIt’s turns out, my issue was that I had nginx on both the host and Docker container, so the host wasn’t forwarding the websocket requests like this. I just removed the host nginx and configured the Docker conf to look at port 80 and it worked!
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[SOLVED] How to configure Lemmy instance nginx proxy for websockets?English1·2 years agoSo looking at this again now, am I taking that whole block and adding it to the container’s nginx.conf? If so, does that mean I have to change what port it’s currently listening to (because there’s already a rule in the file for port 80)?
There’s a comment in that server rule that says “this is the port inside docker” and a comment immediately after that says “this is facing the public web”, which confuses me.
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[SOLVED] How to configure Lemmy instance nginx proxy for websockets?English0·2 years agoThe one meant for the Docker container or the one on the host?
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[SOLVED] How to configure Lemmy instance nginx proxy for websockets?English1·2 years agoI think this is where my lack of experience with Docker is showing.
I spun up a DO droplet and installed nginx, Docker CE, and Docker Compose. Then I went through the instructions on the page you linked to and it set it up just fine but when I went to my droplets IP address it wouldn’t connect. I had to add a config file that pointed traffic coming into the droplet on port 80 to redirect to the Docker container instead. Am I overcomplicating it?
penguin_ex_machina@lemmy.worldOPto Selfhosted@lemmy.world•[SOLVED] How to configure Lemmy instance nginx proxy for websockets?English0·2 years agoI seem to be having a lot of lag at the moment, and my post was created twice so I’m just going to delete the other one and start from here…
So I have this set up per the instructions. My instance is on a Digital Ocean instance, and I’m using nginx on the host to point to
localhost:1235
, but that’s about all that conf file is doing. Is there something else I need to do?
So…it’s working now? I haven’t touched anything yet, but I just checked my instance again and it works perfectly fine on desktop now. It always worked through Voyager, so I was able to let people know there was an issue. If it comes back I’ll try some of these suggestions to find a more permanent fix.