Orban

joined 1 year ago
 

Hey guys, i have got a really weird bug going on. I have set up my nextcloud container and been trying to upload to it. Everything works just fine as long as i dont want to upload from my phone from my /DCIM/camera. If i upload form my jerboa or whatsapp or any folders it works just fine. I have gave every permission and tried different versions as well.

Could this be a server-side problem or what?

[–] Orban@lemmy.world 2 points 1 year ago (1 children)

Thank you, now I'm getting to know cloudflare.At the moment there is some problem with a redirecting loop, but as I read itcould be a problem with my nginx config and https. Either way thank you

[–] Orban@lemmy.world 1 points 1 year ago

Yeah I figured some port was not enabled

 

Hey guys, thanks to some of you I was able to set up my lemmy instance. Its working flawlessly. But here comes my new question:

From a security perspective, is it less secure and less anonymous this way, right? I mean with an account on any other instance you would be kinda insivisble if you use a VPN and a alias email without any trace back to yourself. But with an own instance anybody can check where is your server located, therefore you would be less anonym. Right?

[–] Orban@lemmy.world 1 points 1 year ago (2 children)

Alright now im getting

Error!

There was an error on the server. Try refreshing your browser. If that doesn't work, come back at a later time. If the problem persists, you can seek help in the Lemmy support community or Lemmy Matrix room.

but thats progress

[–] Orban@lemmy.world 3 points 1 year ago (1 children)

docker compose up -d

Jesus man that was it. docker compose up -d solved it. Thank you so much

[–] Orban@lemmy.world 1 points 1 year ago (1 children)

Yeah its from here

[–] Orban@lemmy.world 3 points 1 year ago (9 children)

Here is my docker-compose.yml

spoilerversion: "3.7"

services: proxy: image: nginx:1-alpine ports: # actual and only port facing any connection from outside # Note, change the left number if port 1236 is already in use on your system # You could use port 80 if you won't use a reverse proxy - "8536:8536" volumes: - ./nginx_internal.conf:/etc/nginx/nginx.conf:ro,Z restart: always depends_on: - pictrs - lemmy-ui

lemmy: image: dessalines/lemmy:latest hostname: lemmy restart: always environment: - RUST_LOG="warn" volumes: - ./lemmy.hjson:/config/config.hjson:Z depends_on: - postgres - pictrs

lemmy-ui: image: dessalines/lemmy-ui:latest environment: - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536 - LEMMY_UI_LEMMY_EXTERNAL_HOST=* - LEMMY_UI_HTTPS=true volumes: - ./volumes/lemmy-ui/extra_themes:/app/extra_themes depends_on: - lemmy restart: always

pictrs: image: asonix/pictrs:0.4.0-rc.7 # 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 environment: - PICTRS_OPENTELEMETRY_URL=http://otel:4137 - PICTRS__API_KEY=lemmy1234
- RUST_LOG=debug - RUST_BACKTRACE=full - PICTRS__MEDIA__VIDEO_CODEC=vp9 - PICTRS__MEDIA__GIF__MAX_WIDTH=256 - PICTRS__MEDIA__GIF__MAX_HEIGHT=256 - PICTRS__MEDIA__GIF__MAX_AREA=65536 - PICTRS__MEDIA__GIF__MAX_FRAME_COUNT=400 user: 991:991 volumes: - ./volumes/pictrs:/mnt:Z restart: always deploy: resources: limits: memory: 690m

postgres: image: postgres:15-alpine hostname: postgres environment: - POSTGRES_USER=lemmy - POSTGRES_PASSWORD=lemmy1234
- POSTGRES_DB=lemmy volumes: - ./volumes/postgres:/var/lib/postgresql/data:Z - ./customPostgresql.conf:/etc/postgresql.conf restart: always

postfix: image: mwader/postfix-relay environment: - POSTFIX_myhostname=lemmy.domain.com restart: "always"

[–] Orban@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (10 children)

Im using centos, everything is up to date with the latest versions.

or you could remove logging references from file (these x-logging lines in each service and whole section on top of file)

Im getting the same error

6
submitted 1 year ago* (last edited 1 year ago) by Orban@lemmy.world to c/selfhosted@lemmy.world
 

Hey guys, im writing here because i'm really out of options and ideas. I have been trying to set up my lemmy instance in docker put i keep failing at the first step. I have filled every {{}} detail and still getting this error:

The Compose file './docker-compose.yml' is invalid because: Invalid top-level property "x-logging". Valid top-level sections for this Compose file are: version, services, networks, volumes, secrets, configs, and extensions starting with "x-".

You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.

I have tried to edit the version number, even deleting it but then im getting this:

The Compose file './docker-compose.yml' is invalid because: Unsupported config option for x-logging: 'options' Unsupported config option for services: 'proxy'

Do you have any idea?

Edit: Thank you all for the ideas. Actually the docker compose up -d solved it!

[–] Orban@lemmy.world 2 points 1 year ago
[–] Orban@lemmy.world 1 points 1 year ago

I kept getting an error about lemmy ui has been moved. But I could make it with ./deploy.sh -w 0.18 -f

 
[–] Orban@lemmy.world 11 points 1 year ago* (last edited 1 year ago) (2 children)

How dare you bring logic into this

[–] Orban@lemmy.world 0 points 1 year ago (1 children)

If i know right, they think the sun has much less power than usual, so it works like a spotlight. So its light wont reach the territories under the moon

[–] Orban@lemmy.world 1 points 1 year ago

Comeon man.. turtles, infinite amount of turtles

 
 
view more: next ›