How to Enable Advanced Configuration for Matrix .well-known Paths in Zoraxy?

[gabriellxxix]

Hi everyone,

I’ve been working on setting up .well-known verification for my Matrix server, and I ran into some challenges when attempting to use a static web server like Zoraxy. My goal was to serve the .well-known/matrix paths with proper responses. Here’s a breakdown of my experience and a working solution I found using Nginx Proxy Manager (NPM):

The Issue with Zoraxy
Initially, I configured Zoraxy to handle .well-known/matrix/server and .well-known/matrix/client paths through virtual directories. While the server endpoint worked correctly, returning the expected JSON response, the client endpoint consistently failed with an error:

{"errcode":"M_NOT_FOUND","error":".well-known not available"}g

Despite extensive configuration attempts and research, I couldn’t find a way to make Zoraxy handle the client endpoint reliably. It seems Zoraxy lacks an easy mechanism for advanced custom responses (e.g., specific JSON payloads) under its current architecture.

Working Solution Using NPM
After switching to Nginx Proxy Manager, I managed to achieve the desired setup with the following configuration added under the Advanced tab for the proxy host (as shown in the attached screenshot):

location /.well-known/matrix/server {
    default_type application/json;
    return 200 '{"m.server": "matrix.example.com:443"}';
}

location /.well-known/matrix/client {
    default_type application/json;
    return 200 '{"m.homeserver": {"base_url": "https://matrix.example.com"}, "m.identity_server": {"base_url": "https://vector.im"}}';
}

This configuration serves the appropriate JSON responses for both the server and client endpoints, allowing .well-known verification to pass successfully. The setup process in NPM was straightforward and flexible for adding custom configurations like these.

Proposed Feature Suggestion for Zoraxy
Given this experience, I’d like to suggest a feature improvement for Zoraxy to include advanced configuration support, similar to what NPM offers in its Advanced tab. For instance, a feature that allows users to directly specify custom locations and define JSON responses or headers would greatly enhance Zoraxy’s usability for scenarios like .well-known verification.

Remaining Questions
Although I resolved my issue by using NPM, I’m curious if anyone here has successfully set up .well-known verification using Zoraxy. Specifically:

Are there alternative methods or plugins that enable advanced configurations in Zoraxy?
Have I overlooked an existing way to achieve this setup within Zoraxy’s capabilities?
I’d love to hear your thoughts or experiences on this topic! Any insights would be greatly appreciated.

Thank you in advance for your advice and suggestions!