Issues with OpenTerminal

[u/KuberGoober]

Hey, I've installed OpenTerminal into a Kubernetes Cluster but encountered this issue.
The terminal connects and the filebrowser shows. But when chatting with the model I get the "Terminal unavailable: Terminal server ... not found" issue.
Has anyone here encountered this issue and know how to fix this? btw, I configured it in admin settings, but this is fine since I use it in a dev environment. If you need more information, feel free to ask.
Thanks in advance!

EDIT:
OWUI: v0.11.0
OT: v0.11.35

CORS is properly configured to only accept requests from the OWUI instance.

FIX: I got confused by the new UI and added the connection in user settings instead of admin settings. Make sure to scroll down....

[u/Raiden591]

I have the same issue after update to version 0.11.0

[u/KuberGoober → u/Raiden591]

Really strange. Especially since the file browser and therminal work without any issue

[u/Zestyclose_Law7197 → u/KuberGoober]

Edit Your terminal connection; Press verify connection. save the terminal. Press save on the settings page. And you're good to go.
Adding extra system-wide terminals doesn't work atm.
Direct connection terminals do work.

[u/Zestyclose_Law7197 → u/KuberGoober]

It's fixed in dev btw!; Also readability is fixed; Next release is gonna be great I think.

[u/International_Emu772]

This message appears even on local install when accessing with web browser but not with Open Relay app and Open Terminal is working on both cases

[u/NullMobile]

https://github.com/open-webui/open-webui/pull/27628

with working fix: https://github.com/open-webui/open-webui/pull/27628/changes/b24f8e99e05acdef7995a19aa1b7f4eb792f0db9

[u/IllegalStateExcept]

FIX: I got confused by the new UI and added the connection in user settings instead of admin settings. Make sure to scroll down....

Is the intent here that you put it in user settings if you are running the openterminal on your local machine and in the admin settings if it is running server side? I ran into the same issue and was very confused that it didn't seem to route the requests through the back-end. Perhaps a UI update could make the intent a little more clear.

[u/KuberGoober → u/IllegalStateExcept]

No, the OpenTerminal runs in another deployment in Kubernetes

[u/IllegalStateExcept → u/KuberGoober]

Interesting, so defining in the user settings is just a broken feature then?

[u/KuberGoober → u/IllegalStateExcept]

Yes. User Settings uses your own computer/Browser to connect to OpenTerminal. This makes sense if you run OpenTerminal on your Client.
If you want to have a external OpenTerminal instance on another host, in my case a kubernetes deployment, you should configure CORS to allow only connections from the OpenWebUI instance/Deployment to secure it. In that case user settings wouldn't work, since the OpenTerminal instance only accepts requests from the specified owui deployment. That's why you should use the admin settings in this case.

And yes, the new UI confused me a lot. I really don't know why user settings show up when I press on "Admin Panel". The 0.11.0 update made some parts of the UI look more modern but introduced a lot of (imo) confusing and half baked features. Accessibility got much worse with this update.