Manager access via android app not working on basic local instalation

[Maik]

Hello:
A few months ago, I started working with OpenRemote as part of my final degree project at university, and I am still in the process of absorbing and understanding all the information in the official documentation. I have successfully deployed a prototype on a local server, which can be accessed from the domain op.recuncho.es.

There are still many aspects to configure, but after confirming access to the manager via a web browser, I wanted to test accessing the manager through the official OpenRemote Android app. However, when I try to access it from the official Android OpenRemote app, I encounter this error:

In the official documentation, I read that access to the manager and insight is configured by default in a standard installation. Could it be necessary to perform any additional actions to access the “master” realm from the Android app?

I only have one realm configured in the manager, “master,” and that’s the one I’m trying to access from the Android app. I enter the domain op.recuncho.es/manager and then specify the “master” realm. After following these steps, the app returns the error.

Access from web browser is working:

Thanks in advance for any help.

[martin.peeters]

First of all, welcome to the forum!

Sorry, the documentation might not be clear enough on this.
You need to enter an http or https prefix. The /manager path is not necessary.

Can you try entering https://op.recuncho.es in the “domain” field of the mobile app?

[Maik]

Hello Martin:

I have tried diferents options and get the error “Could not connect to the domain”:

So it seems that in the domain i have to add the app, manager or insight in custom deploiyment. If I enter the domain op.recuncho.es/manager on the following screen. the application requests a realm, and when I input master, it returns the error I mentioned at the beginning of the post.

On the other hand, I tried entering https://op.recuncho.es/manager, and after providing the realm on the next screen, the application returns this other error.

[Maik]

Hello:

@martin.peeters Could the root of the problem be that I am using the master realm to access the manager in a default installation and that I might need to create a realm different from master?

[martin.peeters]

Accessing the master realm is fine, there is no limitation on that.

Can you verify if the https:// address is accessible through the web browser of your phone?
(for example through a web browser)

During the “server finding” process it fetches data from several endpoints such as /api/master/info and /api/master/apps, to change the items in the dropdown menu.
The “Not Found” message is probably a 404 for the web page address not being found.

Otherwise you’ll need to remote debug your phone, to see what Web URL it’s trying to load.
Because for me it’s tough to reproduce this, as all my deployments don’t have this issue

Hope this helps!

[Maik]

Hello @martin.peeters :

Good morning, and Merry Christmas! Thank you very much for all your help. I am still reviewing the issue discussed in this thread. I have ensured that the URL https://op.recuncho.es is accessible from both a computer browser and an Android mobile browser. In both cases, entering that URL redirects the request to:
https://op.recuncho.es/auth/realms/master/protocol/openid-connect/auth?client_id=openremote&redirect_uri=https%3A%2F%2Fop.recuncho.es%2Fmanager%2F&state=771fa079-c792-45f4-8357-054a09857eac&response_mode=fragment&response_type=code&scope=openid&nonce=89d44a9b-8209-4f51-a9dc-77923e891ce6&code_challenge=XcI7hNguMMy9D-ZY2QUaududbPaPWRQ8nL5MG-KwvD0&code_challenge_method=S256, which I understand is handled by the Docker HAProxy.

Access through the official OpenRemote Android app is still unresolved, but I’m working on it. As you mentioned, it seems the issue is that the URL reaching the proxy when making the request through the OpenRemote Android app is incorrect. In the Android app, you first have to provide the domain and finally the realm.

Below, I describe the errors I encounter when trying to configure access via the Android app:

1. If the domain entered is “https://op.recuncho.es”:
   The system returns an error stating it cannot connect to the specified domain.
   

   

2. If the domain entered is “https://op.recuncho.es/”:
   It then asks for the “realm,” and if you click “back,” you can choose the applications detected in the domain, which in my case is only the manager. After entering “master” as the realm, the system returns this error:
   https://op.recuncho.es//manager/?realm=master because: net::ERR_HTTP_RESPONSE_CODE_FAILURE
   It seems there is an extra “/” just before “manager.”

3. If the domain entered is “op.recuncho.es/manager”:
   The system returns this error:
   https://op.recuncho.es/manager.openremote.app/manager/?realm=master because: net::ERR_HTTP_RESPONSE_CODE_FAILURE
   I don’t understand why the app itself adds “manager.openremote.app” to the URL.

4. If the domain entered is “https://op.recuncho.es” or “op.recuncho.es”:
   The system returns an error indicating that it cannot connect to the domain.

Here are some screenshots of the different stages when configuring access for the OpenRemote Android app:

I still need to review what you mentioned about the routes /api/master/info and /api/master/apps. In your tests, are you deploying a standard demo with deploy-composer.yml? This is the file I am using for my deployment, and I wonder if, after the deployment that enables web access, any additional procedures are required to make access via the Android app possible?

[martin.peeters]

Thanks! Time flew by, so I can give you the best wishes for 2025

Yeah this seems to be an issue on our end.
The Android app hasn’t been consistent with custom URLs that are not hosted by ours.

It’s important to know;
The OpenRemote Android app is meant for prototyping / demo purposes. (for easy access)
We don’t recommend it for distribution / production environments.
Instead, you’re able to build a inherited custom app with your own branding and logic.
Sadly there is no documentation on Android yet, but some info can be found here.

However, the issue has been on our radar internally for some time,
so I’ll make sure it gets picked up by the team.

Weird behavior with custom URLs in connection setup