2. YunoHost
3. core
4. Portuguese
5. Browse

2 / 24

/ 24

Unfinished strings without suggestions

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Number of words
• Number of comments
• Number of failing checks
• Key

	Key	English	Portuguese
	diagnosis_found_errors	Found {errors} significant issue(s) related to {category}!
	diagnosis_found_errors_and_warnings	Found {errors} significant issue(s) (and {warnings} warning(s)) related to {category}!
	diagnosis_found_warnings	Found {warnings} item(s) that could be improved for {category}.
	diagnosis_high_number_auth_failures	There's been a suspiciously high number of authentication failures recently. You may want to make sure that fail2ban is running and is correctly configured, or use a custom port for SSH as explained in https://yunohost.org/security.
	diagnosis_http_bad_status_code	It looks like another machine (maybe your internet router) answered instead of your server.<br>1. The most common cause for this issue is that port 80 (and 443) <a href='https://yunohost.org/isp_box_config'>are not correctly forwarded to your server</a>.<br>2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
	diagnosis_http_connection_error	Connection error: could not connect to the requested domain, it's very likely unreachable.
	diagnosis_http_could_not_diagnose	Could not diagnose if domains are reachable from outside in IPv{ipversion}.
	diagnosis_http_could_not_diagnose_details	Error: {error}
	diagnosis_http_hairpinning_issue	Your local network does not seem to have hairpinning enabled.
	diagnosis_http_hairpinning_issue_details	This is probably because of your ISP box / router. As a result, people from outside your local network will be able to access your server as expected, but not people from inside the local network (like you, probably?) when using the domain name or global IP. You may be able to improve the situation by having a look at <a href='https://yunohost.org/dns_local_network'>https://yunohost.org/dns_local_network</a>
	diagnosis_http_nginx_conf_not_up_to_date	This domain's nginx configuration appears to have been modified manually, and prevents YunoHost from diagnosing if it's reachable on HTTP.
	diagnosis_http_nginx_conf_not_up_to_date_details	To fix the situation, inspect the difference with the command line using <cmd>yunohost tools regen-conf nginx --dry-run --with-diff</cmd> and if you're ok, apply the changes with <cmd>yunohost tools regen-conf nginx --force</cmd>.
	diagnosis_http_ok	Domain {domain} is reachable through HTTP from outside the local network.
	diagnosis_http_partially_unreachable	Domain {domain} appears unreachable through HTTP from outside the local network in IPv{failed}, though it works in IPv{passed}.
	diagnosis_http_special_use_tld	Domain {domain} is based on a special-use top-level domain (TLD) such as .local or .test and is therefore not expected to be exposed outside the local network.
	diagnosis_http_timeout	Timed-out while trying to contact your server from outside. It appears to be unreachable.<br>1. The most common cause for this issue is that port 80 (and 443) <a href='https://yunohost.org/isp_box_config'>are not correctly forwarded to your server</a>.<br>2. You should also make sure that the service nginx is running<br>3. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
	diagnosis_http_unreachable	Domain {domain} appears unreachable through HTTP from outside the local network.
	diagnosis_ignored_issues	(+ {nb_ignored} ignored issue(s))
	diagnosis_ip_broken_dnsresolution	Domain name resolution seems to be broken for some reason... Is a firewall blocking DNS requests ?
	diagnosis_ip_broken_resolvconf	Domain name resolution seems to be broken on your server, which seems related to <code>/etc/resolv.conf</code> not pointing to <code>127.0.0.1</code>.