your git ssh client needs to be able to talk to it.
so something has to do portforwarding to the gitea-builtin-ssh server on 3222.
I’m having a similar problem on Kubernetes.
There seem to be so many ways to do this that no one has an opinionated recipe yet.
I don’t know that much about snap, but I would be cautious with your solution:
If I’m not mistaken, current is only a symlink to an actual version.
Thus, your issue will most likely reappear once Gitea is updated (which snap likes to do automatically without any admin knowing), and hence the target of current is changed.