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]: Typo "therefor" #45275

Closed
4 of 8 tasks
raphj opened this issue May 13, 2024 · 1 comment
Closed
4 of 8 tasks

[Bug]: Typo "therefor" #45275

raphj opened this issue May 13, 2024 · 1 comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug

Comments

@raphj
Copy link

raphj commented May 13, 2024

⚠️ This issue respects the following points: ⚠️

Bug description

The following message:

To allow this check to run you have to make sure that your webserver can connect to itself. Therefor it must be able to resolve and connect to at least one its trusted_domains or the overwrite.cli.url.

Needs to be fixed:

To allow this check to run you have to make sure that your webserver can connect to itself. Therefore it must be able to resolve and connect to at least one its trusted_domains or the overwrite.cli.url.

Steps to reproduce

N/A

Expected behavior

N/A

Installation method

None

Nextcloud Server version

master

Operating system

None

PHP engine version

None

Web server

Nginx

Database engine version

MySQL

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

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

@raphj raphj added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels May 13, 2024
@joshtrichards
Copy link
Member

Fixed in #45254
Initially fixed in #45276.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants