Unraid: No internet connection in docker when using Network Type: Custom: br0

[jzhvymetal]

If I install the docker on unraid with Network Type: bridge, connection internet works when using chrome image app. If the docker is Network Type: br0 to assign a IP address other than the main unraid server then there is no internet connection when using chrome image app. If I console inside the docker image internet access is working as I can ping an internet address.

Is there setting that needs to be changed inside Kasm when not using a bridged network?

[github-actions]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[ed-tt]

+1 Im suffering the same issue!

No internet access on any apps or environments within Kasm.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Hielyr]

I'd like to chime in here as well and say that I have the same issue.

I'm using Custom: br0 for my network and have assigned the Kasm docker a dedicated IP address that is different than the Unraid server IP.

None of the Kasm workspaces (apps) have internet access whatsoever.

I've read through Kasm's documentation on bridged network NATing and it unfortunately didn't help much. https://kasmweb.com/docs/latest/how_to/bridged_network_source_nat.html

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[samssausages]

Having similar issues when using a custom IP on my unraid install with mcvlan VLANS.
Can access kasm, kasm has internet access to install itself & workspaces.
But none of the internal kasm dockers have internet access. It doesn't appear to hit my firewall, as there are no blocked requests in my firewall logs.
In my firewall logs, I do see the kasm docker create states to web facing IP addresses.

When I'm in a kasm docker, and I try to ping google.com, it does resolve to an IP address, but all the ping requests are dropped.
I'm assuming it's being blocked inside of kasm, or somethign that I need to config there.

[samssausages]

also, by default my firewall blocks ICPM ping requests. When I use a kasm workspace to ping the firewall, I do see the firewall blocked the request.
If I open my firewall to allow ICPM pings (with logging), the firewall log shows the request accepted, but in the kasm workspace there are no responses to the ping requests.
So I'm feeling pretty confident my firewall is configured correctly and the issue lies with my kasm config. Is there a place in kasm where I need to add something like a trusted network?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[ed-tt]

Just a nudge to say this issue still exists. Github bot is stupid.

[j0nnymoe]

This isn't an issue really with the container, Kasm provide information on how to use their workspaces with different connections here: https://www.kasmweb.com/docs/latest/how_to/bridged_network_source_nat.html - While they provide details for how to do this with docker-compose, You'd need to adapt it yourself to unraid.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[TheMoroney]

Would be nice if there was some documentation on how to accomplish this.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[zhqu1148980644]

Same issue, seems like all sub-containers can not even resolve hosts, which causes apps and registery-adding fails in networks.

Error msg in webui when adding registery

message
https://registry.kasmweb.com/ - A valid url needs to be entered

[neoanantha]

+1

host: kasm.domain.com
ingest_date: 202309141724
application: kasm_api
levelname: ERROR
kasm_user_name: [email protected]
process: admin_api_server
client_ip: *.*.*.* <masked>
user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/117.0
message
https://registry.kasmweb.com/ - A valid url needs to be entered

Hitting above issue while trying to add registry

Version 1.14.0

[j0nnymoe]

As I linked above, kasm provide details on how to do this but it's not specific to unraid.

[drizuid]

Would be nice if there was some documentation on how to accomplish this.

the unraid forums would be a good place to document this and share it out, your fellow users would greatly appreciate you.

[drizuid]

Closing as the OP and other affected users were not following the instructions in the readme.