Meaning I just wait a bit and retry later?
Upgraded 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
I 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.
About freaking time. I have it as an option but I hate using it. I’ve been looking for alternatives for a while now because I just expect to lose a couple hundred bucks in “processing” for every project I work on.
I never used Apollo (I’m an Android user) but I tried wefwef for the first time today and I’m surprised at how natural it feels. If this is what Apollo was like I’m sad I didn’t get a chance to experience it.
It looks like email is getting blocked because I need to set up SPF or DKIM. From my postfix logs:
This mail is unauthenticated, which poses a security risk to the 550-5.7.26 sender and Gmail users, and has been blocked. The sender must 550-5.7.26 authenticate with at least one of SPF or DKIM.
Now I’m off to figure that out!
EDIT: It works now! Emails are currently being sent to spam but at least it’s making it to my inbox.
Done. 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.
Ah SHIT. Thanks, doing it now.
I updated my docker-compose.yml
above to the full file. Does that help?
No, I didn’t have anything there. The docs say everything but the login and password are required, but because I’m using the relay package I don’t know what those would be to begin with because I’m not using an external SMTP with an account.
!!! THAT DID IT.
Thank you so much I would have never gotten to that solution on my own. Works beautifully now.
I’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.
“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.
It’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!
I thought the same maybe, but I assumed an actual camera because of context (using the camera’s manual focus and printing out the photo afterwards). @WeirdGoesPro@lemmy.world ? Did I misunderstand?
Disclaimer: I’m not an optician. I do, however, work in advertising and happen to have a number of clients in the lens manufacturing industry. Take what I’m about to say with a grain of salt.
Short answer is, not really.
Diagnosing vision issues is much more complicated than simply “is it in focus”. The shape of the cornea, how your eye physically reacts to light, distance from an object, and disease all have an impact on how you perceive the world around you. That’s why you have things like aberrations, glares, near sightedness, far sightedness, and a plurality of other vision problems. When someone is fitted for glasses or contact lenses, a number of parameters (read, dozens) are required get what is considered a proper “fit”.
There are some similarities between how a camera lens works and our eyes, but you also have to consider that you’re not just looking through the lens itself, you’re focusing on a screen that’s attached to the lens. So, if you can’t focus your eye sight at the distance the screen is at, it doesn’t matter what the camera is seeing, because it’ll look like garbage to you either way.
I used to read a lot more, and I do remember this happening, but it happens a lot for me now with podcasts. I’m a big podcast junkie and I will often find myself going down a rabbit hole of thought and realizing I have no idea what they’re talking about anymore.
Not to hijack the conversation, but once a server is open and set up what are the best ways to attract people to it? Just start telling people about it?
So 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.
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.