processone / processone/docker-ejabberd
ejabberd docker with Tailscale + serve.json
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 101
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
hello ejabberd Dev and community. I managed to run ejabberd docker with Tailscale. I can login to admin portal page but cannot connect to the server with conversations app. here are the compose.yml and serve.json. I know I have missed things which I need a guidance KINDLY
compose.yml
services:
xmpp-tailscale:
image: tailscale/tailscale:latest
container_name: xmpp-tailscale
cap_add:
- NET_ADMIN
hostname: chat
environment:
- TS_AUTHKEY=xyz
- TS_AUTH_ONCE=true
- TS_SERVE_CONFIG=/config/serve.json
- TS_STATE_DIR=/var/lib/tailscale
- TS_CERT_DOMAIN=chat.forest-gentoo.ts.net
networks:
- xmpp
restart: always
volumes:
- xmpp-tailscale-data:/var/lib/tailscale
- ./serve_config/tailscale:/config
xmpp-server:
image: ejabberd/ecs
container_name: xmpp-server
volumes:
- './ejabberd.yml:/home/ejabberd/conf/ejabberd.yml'
restart: always
ports:
- 5443:5443
- 5280:5280
networks:
- xmpp
depends_on:
- xmpp-tailscale
networks:
xmpp:
volumes:
xmpp-tailscale-data:
serve.json
{
"TCP": {
"5443": {
"HTTPS": true
},
"5280": {
"HTTPS": true
}
},
"Web": {
"${TS_CERT_DOMAIN}:5443": {
"Handlers": {
"/": {
"Proxy": "http://xmpp-server:5443"
}
}
}
}
}
kindly need suggestion
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing compose.yml and serve.json together, then inspect the mounted ejabberd.yml configuration and the shared xmpp network. Verify that the Tailscale Serve targets and exposed ports match the server's listeners and the Conversations connection requirements. Done means Conversations can connect successfully while the admin portal remains reachable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100