/kbin Issues : kbinMeta

[+] [email protected] 2 points 2 years ago* (last edited 2 years ago)

[deleted]

[-] [email protected] 1 points 2 years ago

Does the notification system work? I don't see any notifications even though I should.

[-] [email protected] 1 points 2 years ago

It might be turned off in settings. I'm getting notifications.

[-] [email protected] 1 points 2 years ago

Starting to see notifications now. Guess it's fixed?

[-] [email protected] 1 points 2 years ago

Longer comments have a band at the bottom of the text with a double arrow which, when click on it, is meant expand and show the rest of the text. On mobile, it doesn't uncover all the text. Is there an option to disable this feature so that comments are not collapsed?

[-] [email protected] 1 points 2 years ago

Too many posts weren't federating with kbin so I had to make a lemmy account to avoid missing comments from non-kbin communities, so hopefully the federation issues get fixed at some point.

[-] [email protected] 1 points 2 years ago

Hi, not sure if this is the right thread but here goes.

Issue:
Threads do not seem to federate properly.

Description:
Until a month ago or so, submitting a thread to a federated instance (tested on: feddit.it, sh.itjust.works) threw an error page, but the thread was regularly posted. Example: https://feddit.it/post/1868675

As of at least 2 weeks ago, the error page remains but threads do not federate anymore. Example:
https://kbin.social/m/[email protected]/t/546143/Analisi-di-Pezzi-Pop-5-Faith-Hill-The-Way-You

If it can be of help, posts, links and comments seem properly federated to the same abovementioned instances, i.e. appear on target instances within a few seconds. No error displayed when submitting.

Hope this can be addressed sooner or later. Right now I'm using local accounts on those instances to work this around.

[-] [email protected] 1 points 2 years ago

The issue I had with Up/Down Vote, and Boost throwing errors appears to be resolved. Huzzah!!!

[-] [email protected] 1 points 1 year ago

I'm sure you're aware there has been an issue with people/bots spamming CP on some lemmy instances, I'm not sure if I happened to see them before removal, or if removal still isn't federating properly (since I know the admins/mods have been trying to implement additional solutions), either way, these posts were still showing up on all/new last night/early this morning (GMT), so it might just be worth double checking on your end if there is any way to stop this.

[-] [email protected] 1 points 2 years ago

This comment thread is behaving very strangely right now: comments with the same ID are showing up multiple times in different places, and I just received a notification about a reply that I don't see in the thread.

load more comments (3 replies)

[-] [email protected] 1 points 2 years ago

I've been trying to set up my own kbin instance but without success. Is there a way to diable SSL? I'm running the instance on a raspberry pi at home behind a reverse proxy which already handles all the certificates for https. This already works great for my mastodon instance.

I tried installing the docker container and also manually but both times it expects https instead of simple http and I can't seem to find the place to change this. There's no mention of SSL in the nginx configuration file and I don't really have any experience with docker and where to change the configuration in such a container.

[-] [email protected] 1 points 2 years ago

Weirdly enough, the manual installation seems now to work (the website is reachable) but kbin shows me a server error 500 for every site. I don't have mercure installed because I couldn't figure out how (it isn't mentioned in the kbin doc and the mercure website is not really helpful), could that be the problem?

[-] [email protected] 1 points 2 years ago

minor issue but i can load "[email protected]" I can see their threads, but when I reply the reply does not appear on their end

[-] [email protected] 1 points 2 years ago

Has anyone tried creating a KBIN server using the Docker instructions since Saturday? I got a development server running on Saturday and I decided to bring up a production ready version on Sunday, but now I'm running into two errors while creating it.

First:

In these instructions:

$ sudo chown 82:82 public/media
$ sudo chown 82:82 var
$ cp .env.example .env

There is no directory "var" so the chown fails

Second:

When running docker compose build --pull --no-cache

It now fails with this:

=> [php app_php 20/21] RUN rm -Rf docker/ 0.2s
=> ERROR [php app_php 21/21] RUN set -eux; mkdir -p var/cache var/log; if [ -f composer.json ]; then composer dump-autoload --classmap-authoritative --no-dev; compose ...

This also seems to relate to the var directory, and so must be part of a recent change in the build that relates to the var directory.

Can anyone help?

Thanks

[-] [email protected] 1 points 2 years ago

I have tried creating an instance on both Debian 11 and Ubuntu 22.04 with both Docker and the manual steps.

I can get the build to work fine. But at best I get 500 errors with no signs of logs as to why, not in postgres, not in nginx, not in redis or rabbitmq or even syslog.

On Docker i have both the kbin_messenger and kbin container boot looping with an error about creating cache directories. But since the containers are restarting I cant even get into bash on them to see why.

I finally said fuck it and ran the compose for "prod" and the containers start but again, 500 errors.

At this point....i give up i feel. I would love to host an instance and I am familiar with some of these modules (ie: NGINX, redis and postgres) but with how this is built, I dont see where the breakpoint is.

[-] [email protected] 1 points 2 years ago

I operate my own homelab and have a background in SRE, so I figured I'd try out the same. I've wrangled a Mastodon instance install before, so this couldn't be too hard, right?

My approach started by using containers via lxc as a quick and dirty way of getting a development environment that enabled me to figure out if it worked and then see if I could then wrap it into a proper docker container and look at potentially publishing that.

On my first attempt, I did the manual route. I skipped the redis, rabbitmq, and postgres installs as I already operate those elsewhere on the network, but I got everything else running. Unfortunately, I also experienced the 500 errors. Most of the front page loaded, except for the content where the 500 error was displayed. Even with some digging around, I couldn't find a clear path to figuring out what was causing the 500 error, as the Mercure hub was seeing subscribers connect and disconnect. Gave up.

I then figured maybe the docker route might be easier/streamlined. I'm not a fan of duplicating services, but I thought that if the core workflow was solid enough, I could put effort into splitting them apart and go from there. Unfortunately, I don't even get past the docker-compose build for dev. Docker compose hangs forever.

[-] [email protected] 1 points 2 years ago

Yeah. Kbin install made me eat some humble pie for sure. I think someone called me a normie in a lemmy thread describing my troubles. Lol.

To be fair some of the parts like mercure and rabbitmq im unfamiliar with. But it was a stone cold stumper for me and that’s rare. I’m fairly familiar with Linux admin, and even some of the tooling like docker. But I just couldn’t get it to work in a cohesive way. I ran plenty of Linux servers from Drupal instances, Postgres, nginx for all sorts of shit, etc etc.

My lemmy instance took….45 minutes to roll out. Though I already had an Ansible box sitting in my lab.

[-] [email protected] 1 points 2 years ago

The page to manage moderators is broken and returns 503 Service Unavailable. It has been doing this for at least a week. I'm unable to add moderators to the magazines that I created as a result and I could use some help on some of them.

For example: https://kbin.social/m/TodayILearned/moderators

I tried in Chrome, Safari, Firefox and curl. curl returns:

&lt; HTTP/2 503
&lt; server: Varnish
&lt; retry-after: 0
&lt; content-type: text/html
&lt; accept-ranges: bytes
&lt; date: Mon, 26 Jun 2023 21:14:46 GMT
&lt; via: 1.1 varnish
&lt; x-served-by: cache-bfi-krnt7300043-BFI
&lt; x-cache: MISS
&lt; x-cache-hits: 0
&lt; x-timer: S1687814086.621395,VS0,VE1271
&lt; strict-transport-security: max-age=31557600
&lt; alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
&lt; content-length: 11206

Any word on when this might be resolved?

[-] [email protected] 1 points 2 years ago

Just came here from reddit, so I'm not sure if this is the best place to post this but anyway... Usernames when logging in are case sensitive. This should not be the case because
#1 it's very confusing (I could not figure out why my password was constantly wrong even after resetting it, until i remembered some comment from someone on reddit about case sensitive login issues on some website and tried changing the first letter of my username to lowercase, then it finally worked). I haven't seen any other website work like this.
#2 you're basically allowing people to impersonate others if user account creation thinks usernames with different capitalization are unique names.

Btw, there should be an "Add comment" or "Reply" button up top on the post. At first i thought the thread was locked since there wasn't a reply button, but then i remembered some old forums put it at the bottom of the page, so i scrolled to the bottom, still no reply button. I had to scroll back up through like 4 screens worth of useless footer clutter before i finally found a comment area. This is going to decrease engagement and growth. (I'm on mobile btw). I even tapped on the + button on top to try to add a comment but there was no option. Same with the More button on the post (though it shouldn't be hidden in a More menu since it's a core feature).

/kbin meta