Meta:Babel

← Index of discussion pages

Babel

archives (latest) →

This is the general discussion forum for Meta (this wiki). Before you post a new comment please note the following: You can comment here in any language. This forum is primarily for discussion of Meta policies and guidelines, and other matters that affect more than one page of the wiki. If your comment only relates to a single page, please post it on the corresponding discussion page (if necessary, you can provide a link and short description here). For notices and discussions related to multilingualism and translation, see Meta:Babylon and its discussion page. For information about how to indicate your language abilities on your user page ("Babel templates"), see User language. To discuss Wikimedia in general, please use the Wikimedia Forum. Consider whether your question or comment would be better addressed at one of the major Wikimedia "content projects" instead of here.

Wikimedia Meta-Wiki

• About Meta
• Discussion pages
• Request pages
• Policies and guidelines
• Information and statistics
• Categories
• Help pages

Participate:

• How to edit a page
• Meta-Wiki discussion page
• Meta-l mailing list

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.

All Wikimedia projects not working in Chrome

I found that most Wikimedia projects do not work in Google Chrome. It says the connection is "not" secure and it won't let me access (it says it "uses" HSTS). Homewer, they work fine in Firefox. --190.77.192.99 20:53, 28 September 2018 (UTC)

have you tried to clear the browser cache? Ruslik (talk) 20:55, 28 September 2018 (UTC)

Are you always browsing not logged in? In case you are a registered user this might be some script you are using globally. --Base (talk) 21:07, 28 September 2018 (UTC)

@Ruslik0: Does not work, same error again. --190.77.192.99 21:16, 28 September 2018 (UTC)

Hi 190, this is working for me on the current version of Chrome. It is possible someone is intercepting your traffic. Can you examine the SSL certificate and see if it is signed by GlobalSign Organization Validation CA, which is in turn signed by GlobalSign Root CA. — xaosflux ^Talk 02:40, 29 September 2018 (UTC)

@Xaosflux: Unfortunately, it's signed as the first, which Chromium does not trust, but Firefox does. --190.198.158.49 13:59, 29 September 2018 (UTC)

Check your certificate stores to see if you have R1 and R3 from GlobalSign. In many cases, chrome products will rely on the OS certificate store, as opposed to Firefox which has its own certificate store. If your OS has a "root certificates update" pending, this could cause your issue. Do you mind sharing your browser and os version information? — xaosflux ^Talk 14:28, 29 September 2018 (UTC)

@Xaosflux: Windows 7 Service Pack 1 (Google Chrome version 69.0.3497.100). The cert is G2. --190.198.158.49 17:30, 29 September 2018 (UTC)

Hi 190, here is the cert chain I see:

If you don't trust the GlobalSign certificates, you will need to resolve that on your end. You can manually install them from the link above. — xaosflux ^Talk 18:54, 29 September 2018 (UTC)

@Xaosflux: Yet no effect, just the same error. It is missing the "root" certificate. --190.198.158.49 19:18, 29 September 2018 (UTC)

Did you go to the globalsign site, download, and install the root certificates? — xaosflux ^Talk 23:45, 29 September 2018 (UTC)

@Xaosflux: Unfortunately, Windows won't trust GlobalSign Root R3 even if I installed it. Firefox, on the other hand, works correctly. Here's an image. I know it's in Spanish, but here's a translation to English. --190.198.158.49 01:16, 30 September 2018 (UTC)

Hi 191, go to GlobalSign and reinstall R1; then restart your computer and try again. — xaosflux ^Talk 01:34, 30 September 2018 (UTC)

Verifying multiple accounts

A common practice when verifying multiple accounts is to add a short signed note on a user page. To do this on an account with a global page this has to be done here on Meta, but this is not possible here because of an edit filter blocking editing other user pages.

Error: This action has been automatically identified as harmful, and therefore disallowed. If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: Prevent standard users from editing others' user pages

Seems like someone has been overly creative on what needs to be protected. — Jeblad 19:29, 11 October 2018 (UTC)

Hello, @Jeblad: can you let me know which user id you were trying to make the edit with, and which page you were trying to edit when you got hit by that filter? — xaosflux ^Talk 19:37, 11 October 2018 (UTC)

Edited with Agtbot (Agtramp is for testing vandalism at nowiki) on page Jeblad, but newer mind, its not really necessary to add a signature to the page. It is just a common idiom. — Jeblad 20:13, 11 October 2018 (UTC)

@Jeblad: filter 161 blocks this, following a community discussion here that the problems outweighed the good. Users with autopatrol access (such as yourself) are exempt. — xaosflux ^Talk 21:20, 11 October 2018 (UTC)

It will block users from self-declare and verify their alternate accounts. Wikimedia-users has newer been to keen on identification and authentication, so it does not come as a big surprise. — Jeblad 05:12, 12 October 2018 (UTC)

The logged in user can list their other accounts, if they want to 'cross-post' they can use the talk page and provide a diff link on the userpage. — xaosflux ^Talk 14:19, 12 October 2018 (UTC)