10 months ago
Hey, I setup a own docker image which includes Uptime Kuma and Tailscale.
Almost everything works, it connects to tailscale and everything, but I have the following issue:
I can connect from devices in the Tailscale network to railway.
But cannot connect from railway to devices in the Tailscale network.
E.g. I can ping the railway container from my server, but cannot ping my server from the railway container
Does anyone have an idea how I could fix that?
0 Replies
Dockerfile
# Use the Uptime Kuma base image
FROM louislam/uptime-kuma:latest
# Install necessary dependencies for Tailscale
RUN apt-get update && \
apt-get install -y curl iproute2 iptables && \
apt-get clean && rm -rf /var/lib/apt/lists/*
# Download and install Tailscale
RUN curl -fsSL https://tailscale.com/install.sh | sh
# Expose Uptime Kuma port
EXPOSE 3001
# Copy entrypoint script
COPY entrypoint.sh /entrypoint.sh
RUN chmod +x /entrypoint.sh
# Set entrypoint
ENTRYPOINT ["/entrypoint.sh"]
entrypoint.sh
#!/bin/bash
# Start Tailscale with userspace networking and proxy settings
/usr/sbin/tailscaled --state=/var/lib/tailscale/tailscaled.state --socket=/var/run/tailscale/tailscaled.sock --tun=userspace-networking --socks5-server=localhost:1055 --outbound-http-proxy-listen=localhost:1055 &
until /usr/bin/tailscale up --authkey=${TAILSCALE_AUTHKEY} --hostname=${TAILSCALE_HOSTNAME}
do
sleep 0.1
done
# Start Uptime Kuma
node server/server.js
10 months ago
I don't have any ideas, but I am very curious to know the use case for this?
I want to monitor stuff on my server like the Database which I dont wanna expose to the public, and as I already use tailscale to connect to the database from other Servers in my network, I thought about also monitoring via this.
10 months ago
if you already have the knowhow to run databases on your own hardware, why not run kuma there too?
And to avoid my status page going down when everything goes down, I wanna host it externally.
10 months ago
okay gotcha
Because I had stuff going down lately and then I only receive the notifications when everythings back up.
10 months ago
what exactly are the errors you are getting when trying to have kuma ping the stuff you are running on your own hardware?
10 months ago
you said you can't have kuma on railway ping the stuff you run on your hardware, what specifically are the errors though
10 months ago
can you send that as a regular image please
10 months ago
not the most helpful error message, I think you might find the help you need in some kind of tailscale community if one exists?
<:shrug:1217734590547099719> idk, the best place to ask would be here I assumed.
10 months ago
this pertains far more to tailscale than railway tbh
10 months ago
your container does not have a 100x IP, so that would be tailscale
10 months ago
would that not be tailscale itself
10 months ago
I'm looking at it right now and the container ips are 10.x
10 months ago
interface name: railnet0
├─ flags: up, broadcast, multicast
├─ ipv4 address: 10.250.10.122
├─ ipv6 addresses: fd12:74d7:7e85::a4:ee15:a937, fe80::a0aa:eeff:fe15:a937
└─ hardware address: a2:aa:ee:15:a9:37
10 months ago
likely some small misconfiguration with tailscale, do they have a forum or community you can ask?
10 months ago
perfect, let me know how that goes and if you need any railway specific information you can ask me
http://100.83.185.48:60582/
One last quick thing.
It must have some sort of connection. As it knows my tailscale IP, plus my tailscale hostname.
10 months ago
railway does not provide that