Replies: 1 comment 3 replies
-
You don't need to expose the backend to the web, it used to be an option but it's not necessary anymore. In the app you should enter the front url instead of the backurl (the same you would type into your browser). I think that should resolve your issue. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
first of all thanks for this cool project!
I want to self-host kitchenowl but the android app cannot find my server via URL, only via IP and port.
Here is what I did so far:
front
and theback
HTTP ports, but I did not configure any proxying for the usgwi port.front
andback
also have different URLs in my HAproxy.This lead to the current situation:
I can reach the web ui via browser and via the
front
URL just fine. I can log in and everything seems to work so far.If I access the
back
via browser using the IP and port, I get a generic error from kitchenowl saying "Request resource not found", which I interpret as "this URL is not used, but the server is running". I get the same message when I browse toback
via the URL configured in HAproxy.When I use the android app to connect to my server, everything seems to work just fine if I use the IP and the
back
HTTP port. If I use the URL instead, I get a generic ":/ Hmmmmm.... the server could not be reached". The URL I provided to the android app looked likehttps://kitchenowlback.mydomain.tld
.Does anyone know how I can make the app reach my server via a URL?
Thank you all very much!
Beta Was this translation helpful? Give feedback.
All reactions