Proposal to move meet.fsci.in to India - to my Mumbai Server.
With the recent submarine cable cuts and increased latency to Hetzner/Germany/EU, an earlier lingering thought of moving our Jitsi Meet instance to India came back.
From maintaining meet.fsci.in since the time it started (and running personal Jitsi instances even before that), I know resource-wise there isn't an issue co-locating the service along with other services. I have been running a server for my mirror node for quite some time in Mumbai, India, on Contabo. I'm proposing moving meet.fsci.in to my server.
Benefits:
- People behind BSNL, Vodafone Idea, and their downstream ISPs would certainly see the highest benefit due to this latency decrease due to known lower quality of international transit of these ISPs. In general, everyone would get better experience.
- Would save us from issues like when Jio randomly started blocking Hetzner for some reason some years back.
- In any case, as the service wouldn't have to worry about the cost as running another service on the node for me is negligible cost.
To reduce bus factor, I have already discussed it with Ravi Dwivedi. He'll have access to the node if I'm not available and anything goes wrong with Jitsi, though all these years we didn't have to ever nudge the Jitsi service. It mostly works and just need updates, which I in anycase do roughly once a month on my mirror nodes.
Let's say, I keep this proposal open for 1 week and if there's no strong objection, I'll start with the migration process. What're your thoughts?
Pirate Praveen Sun 14 Sep 2025 9:44AM
@sahilister thanks for this offer. I think this would be good. Just document who all have access to the server somewhere. Also this would mean we could scale down the current server since it will only have codema and mediawiki.
Ravi Dwivedi Sun 14 Sep 2025 11:07AM
@sahilister I support the idea.
Akshay Mon 15 Sep 2025 2:22AM
I think the existing server would then have to be downgraded (to reduce cost)? Then, we might have to do some maintenance on the existing codema/wiki too. I'm okay for doing that, but need some coordination.
sahilister Mon 15 Sep 2025 5:11AM
Don't think we would be able to downgrade the node. We'll probably need to spin a new (smaller) node and migrate Mediawiki and Codema to it.
@Akshay would you be attending IndiaFOSS this weekend? If yes, we can sit together and handle it?
Akshay Mon 15 Sep 2025 7:15AM
@sahilister I'll be in Bengaluru, but I won't be attending the event you mentioned. If you're around Indiranagar we can meet.
sahilister Thu 18 Sep 2025 7:54AM
@Akshay seems unlikely for me.
sahilister Tue 23 Sep 2025 6:07AM
Seeing we have an consensus here and a weeks' time for discussion is over, I'll go ahead with the migration this week.
sahilister Tue 23 Sep 2025 12:31PM
TLDR - Jitsi depends on packages which're not part of latest Debian 13/trixie.
We seem to have hit a snag, specifically https://github.com/jitsi/jitsi-meet-debian-meta/issues/13.
Logs for reference:
```
# sudo apt install jitsi-meet
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
Unsatisfied dependencies:
jicofo : Depends: openjdk-11-jre-headless but it is not installable or
openjdk-11-jre but it is not installable or
openjdk-17-jre-headless but it is not installable or
openjdk-17-jre but it is not installable
jitsi-videobridge2 : PreDepends: openjdk-11-jre-headless but it is not installable or
openjdk-11-jre but it is not installable or
openjdk-17-jre-headless but it is not installable or
openjdk-17-jre but it is not installable
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. jitsi-videobridge2:amd64=2.3-249-g9a2123ad4-1 is selected for install because:
1. jitsi-meet:amd64=2.0.10431-1 is selected for install
2. jitsi-meet:amd64=2.0.10431-1 PreDepends jitsi-videobridge2 (= 2.3-249-g9a2123ad4-1)
2. jitsi-videobridge2:amd64=2.3-249-g9a2123ad4-1 PreDepends openjdk-11-jre-headless | openjdk-11-jre | openjdk-17-jre-headless | openjdk-17-jre
but none of the choices are installable:
[no choices]
```
Exploring what options we have here.
sahilister Tue 23 Sep 2025 12:42PM
Jitsi offers installation via Docker https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker. I'm more inclined on getting it through native packages but seems like there's isn't much progress on https://github.com/jitsi/jitsi-videobridge/issues/2357 or https://community.jitsi.org/t/updating-debian-packages-for-trixie-openjdk-21/140486 so really unsure how long this will remain open.
sahilister · Sun 14 Sep 2025 4:53AM
Just a thought - if there's an issue moving the service to personal server, I in anycase already maintain the existing service, which gives me access to IP addresses or such (if that bothers someone), so there isn't any change in existing status quo privacy wise.