Hello! Is it possible to run `flytectl demo start...
# ask-the-community
c
Hello! Is it possible to run
flytectl demo start
on a VSI (virtual server instance) and be able to reach the UI from the public using the public ip of the server? For example:
<public_ip>:30080/console
. I’ve tried this and the demo is running from within the server but i cant seem to reach it from my own browser- do i need to setup a reverse proxy or do something else? I try to navigate to:
<public_ip>:30080/console
and nothing ends up loading despite the demo/sandbox running properly. I also curled the localhost:30080/console from inside the server and I get the html response back. Any sort of help or feedback would be greatly appreciated, thanks!! 🙏
b
I'm pretty sure the demo cluster starts up listening to external addresses as well. You can verify this by typing
docker ps
or
ss -tlpn
and see the 0.0.0.0 address for port 30080
If you have a firewall blocking in between, you can set up ssh tunneling to forward the traffic from ports on your workstation to the server with something like:
ssh -L 30080:127.0.0.1:30080 -L 30002:127.0.0.1:30002 -L 30000:127.0.0.1:30000 user@server_address
and then connect to
<http://localhost:30080>
on your workstation
c
hmmm ok! I’m going to spin up the demo on the remote server again right now and test/try to access it from my workstation. @Björn
so spinning it up via
flytectl demo start
still not accessible from my local workstation. @Björn Going to try the tunnelling but showing this screenshot from within the server for clarity:
(i have label studio up and running as well but on different ports. The label studio instance is working and accessible from my workstation)
b
Weird... 😕 Not unusual that firewalls are opened for port 22,80,443,8080 and not much else however.
It is possible to manually start up the demo container so that is uses port 8080 instead but it's an incomplete solution
c
yeah…the tunnelling didin’t have an effect 😞 hmmm…so odd, unless im missing something vital- not entirely sure 😕
b
are you running tunneling from your workstation to the server?
c
ohhh, actually it reached.
does that imply there is something going on in between (firewall)? @Björn . Also, is this a new home page for the flytectl demo or is there some sort of error despite it reaching…
b
That looks like an error
shouldn't it be http://localhost:30080 in the address bar, or is that hidden in your browser?
c
it’s hidden in the browser!
b
aha, ok 🙂
don't know that browser, but normally you can open up a developer console by pressing f12, and check error messages and network connectivity there
c
@Björn seems like it failed to fetch some data. I wonder if it’s a files/directory issue if there is some volume mounting going on. I could be off here but i ran into this when running label studio via docker compose since docker automatically creates mounted volumes as
root
despite using a different user. if the demo does this as well, could be an issue with not having permissions for some files or folders that are created/mounted via demo start. Not sure though.
b
It fails to load /me for me as well, but it still works...
c
ahh okay.
b
maybe open in incognito mode just to check nothing cached is messing with the browser? Or try another browser? grasping at straws here ^_^
c
@Björn nope. didint work haha. damn…when i click that login button from the screenshot above it goes to an empty page that says “Not found”.
the minio:
<http://localhost:30080/minio/login>
loads properly. just the actual flyte app does not it seems.
s
I came across this screen too, a few times. But reloading the page resolved the issue for me. cc @Jason Porter
c
@Samhita Alla hmmm…reloading not working. It seems like @Brian Tang has a similar issue actually based on his screen shot. I have that same screen. https://flyte-org.slack.com/archives/C01P3B761A6/p1679044302062839
s
I'm seeing this to after upgrading to flyteconsole
>=1.4.8
Created an issue to track it: https://github.com/flyteorg/flyte/issues/3485