penguin_ex_machina 8 months ago • 100%
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.
I don't know when it started, I usually check my instance through the Voyager app and it never showed a problem, but I'm suddenly getting "server error" and 502 bad gateway errors on my instance on desktop. I haven't made any major changes (read, any at all) since I last confirmed it worked on desktop. Checking the logs I don't see any obvious proxy issues but I am getting weird connection issues in `lemmy-ui`: ``` TypeError: fetch failed lemmy-lemmy-ui-1 | at Object.fetch (node:internal/deps/undici/undici:11730:11) lemmy-lemmy-ui-1 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { lemmy-lemmy-ui-1 | cause: ConnectTimeoutError: Connect Timeout Error lemmy-lemmy-ui-1 | at onConnectTimeout (node:internal/deps/undici/undici:6869:28) lemmy-lemmy-ui-1 | at node:internal/deps/undici/undici:6825:50 lemmy-lemmy-ui-1 | at Immediate._onImmediate (node:internal/deps/undici/undici:6857:13) lemmy-lemmy-ui-1 | at process.processImmediate (node:internal/timers:478:21) { lemmy-lemmy-ui-1 | code: 'UND_ERR_CONNECT_TIMEOUT' lemmy-lemmy-ui-1 | } lemmy-lemmy-ui-1 | } ``` Where on earth can I even begin to address this?
penguin_ex_machina 9 months ago • 100%
Meaning I just wait a bit and retry later?
penguin_ex_machina 9 months ago • 100%
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
penguin_ex_machina 9 months ago • 100%
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.
Hi! I'm hoping for some guidance upgrading my instance. I'm still running on v0.17.3 because I ran into some issues upgrading to 0.18 and didn't have time to really figure it out. Now that the current release is v0.19, I have people on my instance asking to upgrade and I don't blame them. Can I simply point Docker compose at the latest release, or do I have to do incremental upgrades? What do I need to look out for with v0.18? Documentation seems to be pretty slim for whatever breaking changes happened during that release cycle and how to deal with them. Any help is appreciated! EDIT: Thank you for all the help! I also had to update pictrs and fix some small config issues and then everything worked as expected. I'm now on 0.19.1!
penguin_ex_machina 1 year ago • 100%
Couldn’t happen to a nicer group of people.
penguin_ex_machina 1 year ago • 100%
They're about 8 years behind the curve though. Just like a client who recently told me they were thinking of getting into NFTs to make some money.
penguin_ex_machina 1 year ago • 94%
It's a bold strategy, Cotton. Let's see if it pays off for them.
penguin_ex_machina 1 year ago • 100%
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.
penguin_ex_machina 1 year ago • 100%
Major woof if true. u/spez is a true business genius.
penguin_ex_machina 1 year ago • 100%
Believe it or not, I spun up an instance to tackle just that at lemmy.graphics. It's still very new but I'd love to see you over there!
penguin_ex_machina 1 year ago • 0%
I've never made a Reddit bot (or used one for that matter) or requested an API key though, so I'm not sure what triggered it for me.
I'm still in the process of moving old saves off my Reddit account and found this gem today. Reddit HQ is coping hardcore, I can't image regular users actually care about this.
penguin_ex_machina 1 year ago • 100%
Following this trend, I would love to see r/superbowl turn into just photos of John Owliver.
I feel like if anyone would appreciate this video as much as I do it'd be you guys. It's a little long but *totally* worth it.
penguin_ex_machina 1 year ago • 100%
"Alright boys, you heard him. He said the magic word. Let's pack our things and get out of here."
penguin_ex_machina 1 year ago • 100%
Ayyyyye don't at me.
...yes. Yes I did.
penguin_ex_machina 1 year ago • 100%
This is the thing that gets me. I'm fine if Reddit wants to diversify revenue, or ask developers to pay a fair share. But the callous disregard for developers, users, moderators, and communities they built is beyond the pale. I don't know how someone can look at the timeline of events and how Reddit has handled this and think, "this is a company that deserves my money". Huffman's comments in the press alone, leaked or not, make him look like a giant d*uche canoe. The moment my saved posts are transferred out I'm gone.
penguin_ex_machina 1 year ago • 100%
100% this. I ended every day doomscrolling until I got bored or the feed accidentally refreshed and sent me back to the top. Now I'm starting to see how bad that was for me.
penguin_ex_machina 1 year ago • 100%
I've felt this so hard the past few days. I would often post on Reddit and never get noticed or find myself just wading through a sea of garbage. Here, it's a lot less noisy but the interactions I do have are noticeably more genuine and that feels great.
penguin_ex_machina 1 year ago • 100%
If you’re a politician or a business owner, you are accountable to your constituents. So a politician needs to be elected, and a business owner can be fired by its shareholders,” he said.
Someone get this man a hearing aid, because he's gone completely tone deaf.
penguin_ex_machina 1 year ago • 100%
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.
penguin_ex_machina 1 year ago • 100%
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.
penguin_ex_machina 1 year ago • 100%
Ah SHIT. Thanks, doing it now.
penguin_ex_machina 1 year ago • 100%
I updated my docker-compose.yml
above to the full file. Does that help?
penguin_ex_machina 1 year ago • 100%
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.
EDIT: I have it working now! I had to set up DKIM and configure my server so Digital Ocean created the proper PTR records. Now email is being sent to spam but at least it's making it through! Hopefully this is the last time I need to bug you guys here about stuff. :) I added a postfix relay to my Lemmy instance and configured the email settings in my `lemmy.conf` file but no matter what I do I keep getting a "no_email_setup" error when I try to test the SMTP server. Is there an obvious step I'm missing? This is my full `docker-compose.yml`: ``` version: "3.3" networks: lemmyexternalproxy: lemmyinternal: driver: bridge internal: true services: proxy: image: nginx:1-alpine networks: - lemmyinternal - lemmyexternalproxy ports: # only ports facing any connection from outside - 80:80 - 443:443 volumes: - ./nginx.conf:/etc/nginx/nginx.conf:ro # setup your certbot and letsencrypt config - ./certbot:/var/www/certbot - /etc/letsencrypt:/etc/letsencrypt restart: always depends_on: - pictrs - lemmy-ui lemmy: image: dessalines/lemmy:0.17.3 hostname: lemmy networks: - lemmyinternal - lemmyexternalproxy restart: always environment: - RUST_LOG="warn,lemmy_server=info,lemmy_api=info,lemmy_api_common=info,lemmy_api_crud=info,lemmy_apub=info,lemmy_db_schema=info,lemmy_db_views=info,lemmy_db_views_actor=info,lemmy_db_views_moderator=info,lemmy_routes=info,lemmy_utils=info,lemmy_websocket=info" volumes: - ./lemmy.hjson:/config/config.hjson depends_on: - postgres - pictrs lemmy-ui: image: dessalines/lemmy-ui:0.17.3 networks: - lemmyinternal environment: # this needs to match the hostname defined in the lemmy service - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536 # set the outside hostname here - LEMMY_UI_LEMMY_EXTERNAL_HOST=localhost:1236 - LEMMY_HTTPS=true depends_on: - lemmy restart: always pictrs: image: asonix/pictrs:0.3.1 # this needs to match the pictrs url in lemmy.hjson hostname: pictrs # we can set options to pictrs like this, here we set max. image size and forced format for conversion # entrypoint: /sbin/tini -- /usr/local/bin/pict-rs -p /mnt -m 4 --image-format webp networks: - lemmyinternal environment: - PICTRS__API_KEY=API_KEY user: 991:991 volumes: - ./volumes/pictrs:/mnt restart: always postgres: image: postgres:15-alpine # this needs to match the database host in lemmy.hson hostname: postgres networks: - lemmyinternal environment: - POSTGRES_USER=lemmy - POSTGRES_PASSWORD=PASSWORD - POSTGRES_DB=lemmy volumes: - ./volumes/postgres:/var/lib/postgresql/data restart: always postfix: image: mwader/postfix-relay networks: - lemmyinternal - lemmyexternalproxy environment: - POSTFIX_myhostname=myhostname.here - POSTFIX_inet_protocols=ipv4 restart: always ``` And my `lemmy.hjson` has this block: ``` email: { smtp_server: "postfix:25" smtp_from_address: "Lemmy <noreply@myhostname.here>" tls_type: "none" } ```
penguin_ex_machina 1 year ago • 100%
!!!! THAT DID IT.
Thank you so much I would have never gotten to that solution on my own. Works beautifully now.
penguin_ex_machina 1 year ago • 100%
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.
penguin_ex_machina 1 year ago • 100%
"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.
Wanted to cross post this here in case someone has had this issue before. Been dealing with this for a couple of days now. cross-posted from: https://lemmy.world/post/94985 > I set up my own personal Lemmy instance yesterday and everything seems to be up and running. I installed it on Docker with SSL enabled on a Digital Ocean droplet. > > The only thing that doesn't seem to work is federated search. I can search local communities, but no matter what I do I can't get it to recognize other instances. I've tried: > > - Searching with the bang prefix (ie, !lemmy_support@lemmy.ml) > - Searching with the whole URL (https://lemmy.ml/c/lemmy_support) > - Keywords ("lemmy support") > > And nothing shows up. I've tried the same search terms multiple times over the past day or so and nothing is changing. My instance has federation and federation debugging enabled (although I can't figure out where the federation debugging outputs yet, because nothing in console log changes), and as far as I can tell there are no errors in the Docker logs that could point me in a specific direction. Where can I start looking to properly debug this? EDIT: I needed to expose my lemmy backend to the proxy network. This answer here helped me get to the solution. Thanks so much! https://lemmy.world/comment/150173
penguin_ex_machina 1 year ago • 100%
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!
penguin_ex_machina 1 year ago • 100%
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?
Let's make a list of our favorite add-ons! For me, I always enable these by default: - Images as Planes - LoopTools - Copy Attributes Menu Then I go out and get my favorite 3rd party add-ons (note, some of these are paid, some are free): - [AutoRig Pro](https://blendermarket.com/products/auto-rig-pro) - [fSpy ](https://fspy.io/) - [Send to Unreal](https://epicgames.github.io/BlenderTools/send2ue/) I'm sure there are others but this list is off the top of my head. What do you all use?
penguin_ex_machina 1 year ago • 0%
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 set up my own personal Lemmy instance yesterday and everything seems to be up and running. I installed it on Docker with SSL enabled on a Digital Ocean droplet. The only thing that doesn't seem to work is federated search. I can search local communities, but no matter what I do I can't get it to recognize other instances. I've tried: - Searching with the bang prefix (ie, !lemmy_support@lemmy.ml) - Searching with the whole URL (https://lemmy.ml/c/lemmy_support) - Keywords ("lemmy support") And nothing shows up. I've tried the same search terms multiple times over the past day or so and nothing is changing. My instance has federation and federation debugging enabled (although I can't figure out where the federation debugging outputs yet, because nothing in console log changes), and as far as I can tell there are no errors in the Docker logs that could point me in a specific direction. Where can I start looking to properly debug this? EDIT: I needed to expose my lemmy backend to the proxy network. This answer here helped me get to the solution. https://lemmy.world/comment/150173
penguin_ex_machina 1 year ago • 100%
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.
penguin_ex_machina 1 year ago • 0%
If this is true does this mean I need to create a second user for myself on my personal instance to get it to register other instances/communities? I can't find anything in search right now that isn't local, no matter how many times I search for something by keyword or URL. I'm loving Lemmy but the federation/cross-instance search is pretty opaque, which is frustrating.
penguin_ex_machina 1 year ago • 100%
This makes sense to me. I was wondering how many were active, engaged communities and how many were shells or ghost towns.
penguin_ex_machina 1 year ago • 100%
That makes sense, but I can't even get my search function to return anything at the moment, even if I copy+paste direct links. Is there another way I can access other servers from my own instance?
penguin_ex_machina 1 year ago • 90%
Wait WHAT.
penguin_ex_machina 1 year ago • 50%
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?
penguin_ex_machina 1 year ago • 100%
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.
penguin_ex_machina 1 year ago • 100%
It blows my mind that Reddit can look at 90% of its communities going dark in some way and think, "yeah, this is fine."
EDIT (AGAIN): Thank you all for the comments on total subs. It's still clearly not 90%, but it still appears to be a significant portion of the active Reddit community. For the interested, check out the comments below for stats. :)
penguin_ex_machina 1 year ago • 0%
The one meant for the Docker container or the one on the host?
penguin_ex_machina 1 year ago • 0%
I might be. See my response here: https://lemmy.world/comment/101425
penguin_ex_machina 1 year ago • 100%
I 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?
I'm playing around with my own instance of Lemmy but I keep getting a "websocket connection failed" error in my console. I'm having a really hard time understanding how to set up nginx for websockets - I'm more used to Apache and not familiar with WS at all. Is there documentation hiding somewhere that will help me set up my proxy forwarding properly?