Skip to content

[FEAT] tofa swag domain conf #817

Open

Description

@Ockingshay

Is this a new feature request?

  • I have searched the existing issues

Wanted change

Sorry, no idea how to ask for this, other than here. Attached if the conf to allow Tofa via swag

Description

tofa.subdomain.conf

Benefits of this PR and context

Working template for tofa media server

How Has This Been Tested?

Written by tofa team and tested by me

Source / References

https://docs.tofa.tv/use-your-own-tunnel.html#swag

Reason for change

Allow Tofa via SWAG

Proposed code change

Version 2026/10/19

make sure that your tofa container is named tofa

make sure that your dns has a cname set for tofa

if tofa is running in bridge mode and the container is named "tofa", the below config should work as is

if not, replace the line "set $upstream_app tofa;" with "set $upstream_app ;"

or "set $upstream_app ;" for host mode, HOSTIP being the IP address of tofa

server {
listen 443 ssl;
listen [::]:443 ssl;

server_name tofa.*;

include /config/nginx/ssl.conf;

client_max_body_size 0;
proxy_buffering off;

location / {
    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;
    set $upstream_app tofa;
    set $upstream_port 33333;
    set $upstream_proto http;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}

}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions