Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Whenever I try to enable sharing translations with server I get the error: "Invalid localization server address specified. Make sure you specified the right server address." And when dpm(xmlrpc_errno()) and dpm(xmlrpc_error_msg()) I get "403" and "Forbidden".
This is happening both with "http://localize.drupal.org" and "https://localize.drupal.org" as server. Is it possible the server is denying me access? I've tried this on two different server setups and on simplytest.me as well all with the same outcome.
Comment | File | Size | Author |
---|---|---|---|
#20 | 2638468.patch | 609 bytes | Gábor Hojtsy |
Comments
Comment #2
Zoltán Balogh CreditAttribution: Zoltán Balogh commentedYes, here too. Currently, the sharing function of the Localization Client module does not work, because the users can not enable the sharing function.
Comment #3
Zoltán Balogh CreditAttribution: Zoltán Balogh commentedhttps://localize.drupal.org/xmlrpc.php -> Error 403 Forbidden.
Please, set the public access of this URL.
Comment #4
Gábor HojtsyComment #5
Gábor HojtsyComment #6
Gábor HojtsyPinged the issue to @drumm. I don't believe I can do anything about this personally.
Comment #7
drummThis looks like a misconfiguration of Fastly.
Comment #8
basic CreditAttribution: basic at Drupal Association commentedif ( req.url ~ "^/xmlrpc.php"
&& req.http.host ~ "^(qa.drupal.org|localize.drupal.org|updates.drupal.org|www.drupal.org|drupal.org)$") {
error 403 "Forbidden.";
}
is our current configuration and has not changed since Dec 03 2015
Comment #9
drummI was thinking it should look more like:
Comment #10
Zoltán Balogh CreditAttribution: Zoltán Balogh commentedCurrent status:
https://qa.drupal.org/xmlrpc.php -> Forbidden
https://localize.drupal.org/xmlrpc.php -> Forbidden
https://updates.drupal.org/xmlrpc.php -> File not found
https://www.drupal.org/xmlrpc.php -> Forbidden
https://drupal.org/xmlrpc.php -> Forbidden
Comment #11
Gábor HojtsyMarked #2653296: Invalid localization server address specified a duplicate.
Comment #12
Zoltán Balogh CreditAttribution: Zoltán Balogh commentedI think, since the current configuration was set (Dec 03 2015) localize.drupal.org/xmlrpc.php is forbidden. This issue created on December 20, 2015 and only the new installations are affected.
Comment #13
tazir1 CreditAttribution: tazir1 as a volunteer commentedI think the issue was just solved.
I just went to: admin/config/regional/translate/client change the "Address of localization server to use" to "https://localize.drupal.org/". Now its working well (translations saved locally and also sent & received by https://localize.drupal.org/ ).
Comment #14
Zoltán Balogh CreditAttribution: Zoltán Balogh commentedYou tried to submit the form at admin/config/regional/translate/client? If you set the "Address of localization server to use" to "https://localize.drupal.org/" before than Dec 03 2015, then that is ok, sharing of the translations works well. Try to submit that form, please, and you will see the error message: Invalid localization server address specified. Make sure you specified the right server address.
I think, in your case the "l10n_client_server" variable already set, so the translation interface is works well. But if you create a new Drupal installation, this variable is empty, and you can not set, because you can not submit the form at admin/config/regional/translate/client without error, and the "l10n_client_server" variable stay empty, and the sharing of translations does not works.
Temporary solution:
drush vset l10n_client_server https://localize.drupal.org/
Comment #15
Gábor HojtsyBut sending the translations itself works with the same xmlrpc endpoint, why is that not a 403 then?
Comment #16
drummI see the default setting hasn't been updated to
https://localize.drupal.org
. The XML-RPC requests do go throughdrupal_http_request()
which seems to have trouble with https and redirects to https in some configurations. See also #1538118: Update status does not verify the identity or authenticity of the release history URL. Making https default will remove any redirection-related issues.I'm not aware of any recent changes on our end.
Comment #17
Zoltán Balogh CreditAttribution: Zoltán Balogh commentedI update my opinion, sending the translations itself does not works too. 403: Forbidden...
Comment #18
robertgarrigos CreditAttribution: robertgarrigos commentedI had this problem with a new installation but setting the server with drush
drush vset l10n_client_server https://localize.drupal.org/
solved the problem. When translating I get the message
Translation sent and accepted by https://localize.drupal.org/.
Comment #19
Neograph734Cross posting from #2705877: Fix instances of wrong localize.drupal.org defaults and other outdated http links:
I managed to get this working with Drush, but setting is via the UI at
admin/config/regional/translate/client
worked fine as well. Just append a slash to the default variable.The strange thing is that the Localization client module seems to always appends
/xmlrpc.php
to the server URL:So
http://localize.drupal.org/xmlrpc.php
(the default) doesn't work, buthttp://localize.drupal.org//xmlrpc.php
does? It at least solves the problem.Comment #20
Gábor Hojtsy#2705877: Fix instances of wrong localize.drupal.org defaults and other outdated http links is now fixed for Drupal 7 and 8. We should have an update path in localization client on 7 to update existing sites. I'm moving this now to the localization client queue. This is the upgrade path.
Comment #23
Honza Pobořil CreditAttribution: Honza Pobořil as a volunteer commentedWill be nice to make a release with this fixes.