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

Client connection to Freedomotic should be secure #159

Closed
amenak77 opened this Issue Aug 29, 2018 · 7 comments

Comments

Projects
None yet
2 participants
@amenak77

amenak77 commented Aug 29, 2018

Actual client HTTP connection should be changed into HTTPS (Hyper Text Transfer Protocol Secure)

@mcicolella mcicolella changed the title from Client connection to Freedomitic should be secure to Client connection to Freedomotic should be secure Aug 30, 2018

@amenak77

This comment has been minimized.

Show comment
Hide comment
@amenak77

amenak77 Sep 6, 2018

bad_login_info

After updating my vue webapp repo, now I have this connecting problem "ERROR Bad login information"

amenak77 commented Sep 6, 2018

bad_login_info

After updating my vue webapp repo, now I have this connecting problem "ERROR Bad login information"

@amenak77

This comment has been minimized.

Show comment
Hide comment
@amenak77

amenak77 Sep 6, 2018

conn_refused

The error rises using every kind of browser (even from mobile); in console I have a warning "Failed to load resource: net : : ERR_CONNECTION_REFUSED" which is a typical block warn between client and server; so I checked antivirus, firewall, scan for viruses: nothing different.
Maybe an answer could be here: https://www.google.it/amp/s/www.wired.com/story/google-chrome-https-not-secure-label/

amenak77 commented Sep 6, 2018

conn_refused

The error rises using every kind of browser (even from mobile); in console I have a warning "Failed to load resource: net : : ERR_CONNECTION_REFUSED" which is a typical block warn between client and server; so I checked antivirus, firewall, scan for viruses: nothing different.
Maybe an answer could be here: https://www.google.it/amp/s/www.wired.com/story/google-chrome-https-not-secure-label/

@amenak77

This comment has been minimized.

Show comment
Hide comment
@amenak77

amenak77 Sep 6, 2018

This review says that after last win 10 update, chrome's (ver 68 up) warnings about insecure HTTP connections become block about sensible data (in this case password content) in order to avoid sensible data theft. Linux seems immune to this "problem". Suggestions? PD If so, fixing issue #159, could be urgent

amenak77 commented Sep 6, 2018

This review says that after last win 10 update, chrome's (ver 68 up) warnings about insecure HTTP connections become block about sensible data (in this case password content) in order to avoid sensible data theft. Linux seems immune to this "problem". Suggestions? PD If so, fixing issue #159, could be urgent

@amenak77

This comment has been minimized.

Show comment
Hide comment
@amenak77

amenak77 Sep 7, 2018

multibr_noconn

I've compliled client's project and updated dist file into webserver plugin. I have connection error via localhost:8090 with every browser except chrome; ever and ever strange....

amenak77 commented Sep 7, 2018

multibr_noconn

I've compliled client's project and updated dist file into webserver plugin. I have connection error via localhost:8090 with every browser except chrome; ever and ever strange....

@amenak77

This comment has been minimized.

Show comment
Hide comment
@amenak77

amenak77 Sep 7, 2018

To be completely honest, client works with chrome, but no tooltips; some remaining data into cache, maybe? Could anyone try to reproduce this error with win 10 please? Thanks. PD actual dailybuild is number 275; could it be a problem in your opinion? Thanks again

amenak77 commented Sep 7, 2018

To be completely honest, client works with chrome, but no tooltips; some remaining data into cache, maybe? Could anyone try to reproduce this error with win 10 please? Thanks. PD actual dailybuild is number 275; could it be a problem in your opinion? Thanks again

@amenak77

This comment has been minimized.

Show comment
Hide comment
@amenak77

amenak77 Sep 8, 2018

After toggling AV settings, this last problem vanished; but I already have bad login with compiled client project; I really hate auto settings

amenak77 commented Sep 8, 2018

After toggling AV settings, this last problem vanished; but I already have bad login with compiled client project; I really hate auto settings

@amenak77

This comment has been minimized.

Show comment
Hide comment
@amenak77

amenak77 Sep 11, 2018

Thanks to virus defender and his magic self changing parameters I've lost days to fix something already fixed until last week. Now no more bad login error with compiled client project. Sorry for this. It is not a HTTP/HTTPS problem

amenak77 commented Sep 11, 2018

Thanks to virus defender and his magic self changing parameters I've lost days to fix something already fixed until last week. Now no more bad login error with compiled client project. Sorry for this. It is not a HTTP/HTTPS problem

@mcicolella mcicolella closed this Sep 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment