3.4.0-8 DOI Crossref registration points to server IP instead of domain address

Software Support
1

Hi

I’m using OJS 3.4.0-8. OJS Crossref assignment and registration process seems to work correctly but the address registered with Crossref uses the IP address of the OJS server instead of the domain name address.

DOI as shown in OJS
https://doi.org/10.20851/xbmjmz08

First Crossref registration (done from OJS 3.4.0-8, logged in a administrator)
result on 14-Mar-2025

<?xml version="1.0" encoding="UTF-8"?>

<doi_batch_diagnostic status=“completed” sp=“bstn-prod-ds-04”>
<submission_id>1683057795</submission_id>
<batch_id>_1741928372</batch_id>
<record_diagnostic status=“Success”>
10.20851/xbmjmz08
Successfully added
</record_diagnostic>
<batch_data>
<record_count>1</record_count>
<success_count>1</success_count>
<warning_count>0</warning_count>
<failure_count>0</failure_count>
</batch_data>
</doi_batch_diagnostic>

This DOI pointed to
https://10.33.12.105/index.php/main/article/view/42
and failed “The server at 10.33.12.105 is taking too long to respond”

It should point to
https://www.jmro.org.au/index.php/main/article/view/43

DOI was deregistered and re-registered on 18-Mar-2025 (done from OJS
3.4.0-8, logged in as journal manager)

Second re-registration result

<?xml version="1.0" encoding="UTF-8"?>

<doi_batch_diagnostic status=“completed” sp=“bstn-prod-ds-03”>
<submission_id>1684429460</submission_id>
<batch_id>_1742280434</batch_id>
<record_diagnostic status=“Success”>
10.20851/xbmjmz08
Successfully updated
</record_diagnostic>
<batch_data>
<record_count>1</record_count>
<success_count>1</success_count>
<warning_count>0</warning_count>
<failure_count>0</failure_count>
</batch_data>
</doi_batch_diagnostic>

Still maps to
https://10.33.12.105/index.php/main/article/view/42
and failed

DOI should map to
https://www.jmro.org.au/index.php/main/article/view/43

Does anyone know why this is happening and what to do about this?

2

Hi @elhay,

I wonder if the base_url in your config.inc.php is set to this IP rather than your domain name? Are you able to check on this?

-Roger
PKP Team

3

IP addresses starting with 10. are not public and not routable. I’m not sure how you configured your server.

4

The variable base_url has been set to the value “https://www.jmro.org.au/jmro3” and that resolves to the correct page.

2 Likes
5

BTW, thanks, @rcgillis.

6

Hi Roger, is there anything else that you suggest I could check which might explain this error? Is it possibly the DOI handling by OJS that is causing it? I’m clutching at straws here.
Thanks

7

Hi @elhay,

No - sorry - I’m not sure what to suggest if you’ve already checked base_url setting appears to be correct. Paging my colleague @AhemNason - to see if he might have some suggestions.

-Roger
PKP Team

8

Thanks for your trouble.

9

Hi @elhay, the advice in here is what I’d have given you. It sounds like some configuration is sending you to the wrong place. Have you tried re-deposting the DOI via the plugin to see if that corrects the issue? If this DOI was registered during a migration or something, that base_url might not have been configured at the time.

If you still have issues, I’d contact Crossref to see if they have any ideas. Do all your DOIs do this or just this one?

Mike
PKP

1 Like
10

Hi Mike. I have redeposited all the DOIs after checking that base_url variable was correctly set. Most of the DOIs do this but not all. I can’t see any pattern there either. The repots from CrossRef show “success” for all of them.

11

Further to my last msg: I exported the xml Crossref submission file for a DOI that (wrongly) points to …10.33.12.105… It looks like this

<?xml version="1.0" encoding="utf-8"?>

<doi_batch xmlns=“http://www.crossref.org/schema/5.3.1” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:jats=“http://www.ncbi.nlm.nih.gov/JATS1” xmlns:ai=“http://www.crossref.org/AccessIndicators.xsd” version=“5.3.1” xsi:schemaLocation=“http://www.crossref.org/schema/5.3.1 https://www.crossref.org/schemas/crossref5.3.1.xsd”>

_1743127907 20250328124147000 Sylvan ELHAY sylvan.elhay@adelaide.edu.au The University of Adelaide Journal of Music Research Online J. Mus. Res. Online 1836-8336 08 10 2023 13 Mahler and His Programs vis-à-vis Strauss Joseph P Jones Gustav Mahler had, by the late 1880s, achieved considerable prestige as a conductor, yet Richard Strauss’s early success as a composer of tone poems earned him wider fame and fortune. Around the time of Strauss’s triumphant premieres of Don Juan and Tod und Verklärung, Mahler was securing performances of his own programmatic orchestral works, the Symphonisches Gedicht in zwei Teilen and Todtenfeier. After disappointing results, he revised both, adding descriptive movement titles and other programmatic details, seemingly following Strauss’s lead. But further unsuccessful performances followed and Mahler grew wary of publicly sharing such descriptions of his works. The so-called ‘Munich Declaration’ of 1900 in which he denounced the programme seemed to react to this negative reception, which stood out in stark relief compared to the acclaim Strauss received.Scholars have long reflected on Mahler’s comments on his programs, but the extent to which his adoption and subsequent rejection of such descriptions was influenced by Strauss has remained elusive. Viewing the early symphonies against the backdrop of works such as Strauss’s Also sprach Zarathustra, this article illuminates how Mahler’s stance on the descriptive programme shifted. Later he was more concerned with comprehension and with setting himself apart from Strauss. But Mahler’s earlier approaches to his own programmatic compositions, including what he chose to share publicly, were clearly bound up with Strauss’s own creative output and suggest envy of his rival’s success and frustration with his own failures. 02 20 2023 10.20851/3gkd3s34 https://www.jmro.org.au/index.php/main/article/view/52 https://www.jmro.org.au/index.php/main/article/download/52/46 https://www.jmro.org.au/index.php/main/article/download/52/46

Then resubmitted the DOI to Crossref and am now waiting to see if it will work. Can’t see any reference to 10.33.12.105 in the xml file generated by OJS 3.4.0-8

12

This topic was automatically closed after 11 days. New replies are no longer allowed.