Mastodon Account Creation #5

New issue

Closed

opened 2024-03-22 14:43:41 +01:00 by Ghost · 0 comments

Ghost commented

2024-03-22 14:43:41 +01:00

From @taeer:

This is now implemented in https://git.fediversity.eu/taeer/mastodon-deployment.

The problem was that mastodon only likes to be accessed from port 443, but you can't forward port 443 in qemu so easily.

The initial solution was to use a proxy server connected to the VM, and then configure firefox to use that proxy server. This was a ton of manual steps, though.

It turns out that in development mode, you can set services.mastodon.enableUnixSocket = false, and then directly access mastodon on port 55001 (bypassing nginx entirely). If I recall correctly I had tried each of these separately but not at the same time.

In any case, this suggests that the problem may be with nginx not with mastodon itself.

For now though, we have a way to create accounts.

From @theophane:

Paired with @taeer on this today.

After a painful debugging session, it turns out that Mastodon doesn't like being exposed on a port other than 443. Accessing it on port 443 fixes the issue (but is rather painful for a local VM-based deployment)

From @taeer: This is now implemented in https://git.fediversity.eu/taeer/mastodon-deployment. The problem was that mastodon only likes to be accessed from port 443, but you can't forward port 443 in qemu so easily. The initial solution was to use a proxy server connected to the VM, and then configure firefox to use that proxy server. This was a ton of manual steps, though. It turns out that in development mode, you can set services.mastodon.enableUnixSocket = false, and then directly access mastodon on port 55001 (bypassing nginx entirely). If I recall correctly I had tried each of these separately but not at the same time. In any case, this suggests that the problem may be with nginx not with mastodon itself. For now though, we have a way to create accounts. From @theophane: Paired with @taeer on this today. After a painful debugging session, it turns out that Mastodon doesn't like being exposed on a port other than 443. Accessing it on port 443 fixes the issue (but is rather painful for a local VM-based deployment)

Ghost added this to the WP2: D2.1 – Software release test environment milestone 2024-03-22 14:43:41 +01:00

Ghost added the

WP2

label 2024-03-22 14:43:41 +01:00

Ghost added this to the Tweag Board project 2024-03-22 14:45:33 +01:00