Skip to content
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

[Bug]: UI | Low Priority | server not using HTTPS, showing lock icon #6723

Open
5 of 8 tasks
jpdagostino opened this issue May 2, 2024 · 0 comments
Open
5 of 8 tasks

Comments

@jpdagostino
Copy link

⚠️ Before submitting, please verify the following: ⚠️

Bug description

Screenshot showing insecure server connection but with a lock in the Nextcloud desktop client settings panel

Steps to reproduce

  1. Disable HTTPS on the server or connect through HTTP on the desktop client
  2. Log into an account
  3. Open the settings
  4. click on the lock

Expected behavior

Should not show a lock icon, normally representing security. Example:
Screenshot depicting different UI in Firefox for site security

Which files are affected by this bug

Not sure, probably within a resource file dll

Operating system

Windows

Which version of the operating system you are running.

Windows 10 Enterprise N LTSC Version 21H2 (OS Build 19044.4291)

Package

Other

Nextcloud Server version

29.0.0.19

Nextcloud Desktop Client version

3.13.0 (Stable channel)

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Nextcloud Server logs

No response

Additional info

No response

@jpdagostino jpdagostino changed the title [Bug]: server not using HTTPS, showing lock icon [Bug]: UI | Low Priority | server not using HTTPS, showing lock icon May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant