Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
r
refined-analyst-8898
03/22/2023, 11:21 PMI'm enjoying Rancher Desktop so far. Something strange happened between stopping and restarting the app and VM. Now the ingress external IP is different, and it's not reachable from the host machine. I'll thread with more details.
✅ 1
Before the restart, the Traefik ingress external IP was reachable from the Linux host machine and the LAN (192.168.1.0/24).
Now, after the restart, the IP is 192.168.5.15, which doesn't match any IP route on the host machine.
❯ ip route get 192.168.5.15
192.168.5.15 via 192.168.1.254 dev wlp3s0 src 192.168.1.149 uid 1000
cacheI have Rancher Desktop Version 1.8.0 on Ubuntu Linux 22.04.
I believe the problem was that I rebooted after following the Rancher Desktop instructions for Linux, which do not hint that it's necessary to persist the unprivileged ports exception in sysctl.conf. I've sent a PR to add a hint.