-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can' connect to a local network name #34
Comments
Hi. Thanks for reporting the issue. I will have some time in the next days and will have a look into this issue. |
Yes, the current URL validation requires a valid URL. I will fix that in the near future. |
I experience the same issue, after installing today from F-Droid. |
Using the IP address (e.g. HTTPS://192.xxx.x.xxx) the sign in page doesn't load. I guess it's the same issue. |
I will add an advanced mode, where you will be able to specify the target server in a more detailed way. |
@dabru1984 if you can proceed to the webview then it might be something else. |
Thank you! OK for the advanced mode. For the load page, it doesn't load at all, i am using microg, the app is GSF dependent? Maybe I can load the page externally somehow? |
No the app should not be GSF dependent. I will be pushing today a new version with an option to disable URL validation, this should allow connection to local network names. @dabru1984 regarding the IP issue can you retry with port specified? Edit: However, in any case you need to have a valid SSL certificate or you have to import your self signed cert into your Android trust store, see #40. |
Hello @vauvenal5 thank you for the follow up, i have tried and failed because i have a self-signed cert, so I fall into #40 issue. I'll try to follow up and add the certificate in order to proceed. Thanks |
|
Thank you for the help so far but I think I would not use a certificate considering that I need to do it only to use the app... I'll look forward for other possibilities to use it without the certificate... |
I will have to try how it behaves with the browser enabled login flow, feel free to reopen #40. Just in general, have you considered using |
@jkumeboshi / @igor-cali can one of you confirm that connecting to a hostname is now possible with the new option to disable URL validation? So I can close this issue. |
@vauvenal5 I still cannot get to the login, even disabling the URL validation and installing my self-signed certificate on the mobile as discussed in #40. |
Can you provide logcat logs? @jkumeboshi and you are only entering |
@vauvenal5 sorry, but I'm not sure how to do. Maybe logs are not enabled in the release builds from web store?
|
Hi everyone! Can you confirm that your issue still exists in |
@vauvenal5 the issue still exists for me with |
Okay! I will work on implementing the login flow v2, which is based on the system browser instead of an internal web view. This way it should fix this problem since you can reach your Nextcloud from your browsers. However, this might take a while since there will be some changes necessary in the upstream Nextcloud Dart library. See provokateurin/dart-nextcloud#20 |
I just released |
Nothing happens when I tap on the |
You do the following steps, right?
|
I do:
|
Can you retrieve the logcat output? |
Same results for me, now I get no result if I press the "continue" button to start webview and "browser" button.
well, the problem looks like to be that the dart HTTP client doesn't uses the system CA store, probably it uses an internal CA store, such as a .PEM file containing major CA certificates. Ok, I did try to build the source and I've disabled CA cert verification adding following code in main:
I can successfully login in nextcloud and grant access, but later I get following error:
if I add HttpOverrides in ForegroundWorker and NextCloudService too, it works. so definitely it's a CA validation problem. |
Hey! Thanks for the research! I will have to look up if it is possible to make Dart use the System CA store. If this is not possible I will have to think about what the proper approach might be in this case. Adding the ability to disable CA verification in general seems too dangerous. 🤔 |
Strictly speaking this is now equal to #40. |
I click the button, but only a little "Trust Certificate" popup appears, no browser is opened. |
Would you be able to provide me with logcat logs? |
Yessir! |
Yes, but since I installed my CA, I don't have to click any "Proceed Anyway" button, here is a screenshot |
I still don't know how to make this work unfortunately. |
Flutter does not respect the system CAs. So for Flutter this is still a untrusted certificate. However, what I can not get my head around is why the Trust-Dialog is not working. I will improve logging around the cert dialog and push a new version. If @Pato05 could then send me a new logcat we might see something more. |
Sure thing, do I need to download another version? Because in the logcat I sent earlier, I had already clicked trust several times |
I just published |
Sure, I will look into it later. |
Tried it. EDIT: |
@ruben-tura yes, this is expected since I only increased the log output to be able to find the actual issue. |
Oh ok, sorry! |
@vauvenal5 Here is the interested logcat part
|
@Pato05 can you confirm one more thing for me please, does your |
Just published |
It works like a charm! Thank you so much! |
Still does not work for me w/ |
it does work, thanks! |
@igor-cali I just published |
|
I consider this issue closed. |
|
Please re-open if it is still an issue. |
If I use a simple local name (such as HTTPS://nextcloudhost/) in the address instead of a full qualified doman name the application does not connect to the nextcloud server.
The application doesn't even attempt to establish a connection to the server.
The text was updated successfully, but these errors were encountered: