I have a lemmy-ui instance working correctly, fresh ansible install. I haven't configured it yet, but it's up and running and test posts work fine.
I'm mostly interested in lemmyBB, so I installed that according to "Alongside existing Lemmy instance (native)" install instructions.
Everything seems to work fine during install,
systemctl status lemmy_bb.service
shows:
Jan 17 06:51:57 vps-f7b29755 lemmy_bb[484]: [2023-01-17T06:51:57Z INFO rocket::launch_] (FileServer: assets) GET /assets/<path..> [10]
Jan 17 06:51:57 vps-f7b29755 lemmy_bb[484]: [2023-01-17T06:51:57Z INFO rocket::launch] 📡 Fairings:
Jan 17 06:51:57 vps-f7b29755 lemmy_bb[484]: [2023-01-17T06:51:57Z INFO rocket::launch_] Templating (ignite, liftoff)
Jan 17 06:51:57 vps-f7b29755 lemmy_bb[484]: [2023-01-17T06:51:57Z INFO rocket::launch_] Shield (liftoff, response, singleton)
Jan 17 06:51:57 vps-f7b29755 lemmy_bb[484]: [2023-01-17T06:51:57Z INFO rocket::launch_] Site data fetcher (request)
Jan 17 06:51:57 vps-f7b29755 lemmy_bb[484]: [2023-01-17T06:51:57Z INFO rocket::shield::shield] 🛡️ Shield:
Jan 17 06:51:57 vps-f7b29755 lemmy_bb[484]: [2023-01-17T06:51:57Z INFO rocket_dyn_templates::fairing] 📐 Templating:
Jan 17 06:51:57 vps-f7b29755 lemmy_bb[484]: [2023-01-17T06:51:57Z INFO rocket::launch] 🚀 Rocket has launched from http://127.0.0.1:8703
When checking in with a browser, I get 502 Bad Gateway.
This will be impossible to debug without the nginx (or whatever reverse proxy you are using) configuration. Because it looks like lemmybb is running but it is not being served properly.
the only difference is that $lemmybb_domain is replaced with the bb ui domain name. Again, the normal lemmy ui works great, ansible install so everything including config is default.
Is there something with the lemmy backend or UI I'm supposed to configure to let it know that lemmyBB exists?
Loaded: loaded (/etc/systemd/system/lemmy_bb.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2023-01-17 17:55:48 UTC; 3min 42s ago
Main PID: 20609 (lemmy_bb)
Tasks: 2 (limit: 2318)
Memory: 2.8M
CGroup: /system.slice/lemmy_bb.service
└─20609 /opt/lemmyBB/target/release/lemmy_bb
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: [2023-01-17T17:58:24Z INFO rocket::server] GET / text/html:
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: thread 'rocket-worker-thread' panicked at 'called `Option::unwrap()` on a `None` value', src/site_fairing.rs:62:53
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: [2023-01-17T17:58:24Z ERROR _] Handler index panicked.
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: [2023-01-17T17:58:24Z WARN _] A panic is treated as an internal server error.
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: [2023-01-17T17:58:24Z WARN _] No 500 catcher registered. Using Rocket default.
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: [2023-01-17T17:58:24Z WARN lemmy_bb::site_fairing] error sending request for url (http://127.0.0.1:8536/api/v3/site): error trying to connect: tcp connect error: Connection refused (os error 111)
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: [2023-01-17T17:58:24Z INFO rocket::server] GET /favicon.ico image/avif:
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: [2023-01-17T17:58:24Z ERROR _] No matching routes for GET /favicon.ico image/avif.
Jan 17 17:58:24 vps-f7b29755 lemmy_bb[20609]: [2023-01-17T17:58:24Z WARN _] No 404 catcher registered. Using Rocket default.```
like I said, aside from domain name and required variables, everything is default, running a fresh vps. Ansible install for Lemmy, "install along other instance" instructions for lemmyBB.
No messing with ports. Fresh debian 10, debian 11, ubuntu 22, all with the same result: