JOSM unable to connect to OpenGeofiction API server for some users

[alessa@…]

JOSM recently stopped being able to access the API server on OpenGeofiction for a couple of users (including myself), preventing uploads or downloads. In these instances, the failure to validate the API server or download/upload happened with no changes to JOSM or the computers involved. One device was running 18789, another was running 19342, and another user was running 19369.

What steps will reproduce the problem?

1. When API server is set to ​https://opengeofiction.net/api and not OSM
2. Attempting to download an area eventually generates an error message of "Connect time out."
3. Attempting to validate the API separately generates a connection time out ("Connection to API failed" error dialogue box)
4. All devices were brought up to version 19369 and Java ensured to be up to date
5. Continued attempts to download or validate time out

What is the expected result?

Previously, uploads and downloads happened without timing out. Validation did not fail.

What happens instead?

API fails to validate and JOSM fails to connect to OpenGeofiction's API server. In one instance, the following error appeared: Error initializing test ApiCapabilitiesTest: org.openstreetmap.josm.io.OsmApiInitializationException: org.openstreetmap.josm.io.OsmTransferException: java.net.SocketTimeoutException: Connect timed out

Please provide any additional information below. Attach a screenshot if possible.

We have been discussing this as an admin team today to troubleshoot this issue. A few other bits of information that might be useful:

1. In-browser iD edits are possible on the site.
2. Access to OpenGeofiction is possible on the devices in question and even within JOSM (OGF-Carto and OGF-Topo tiles can still be loaded as layers).
3. Doing a command line curl of the API generates the appropriate report, showing connection.
4. There was server maintenance during the intervening period. JOSM may have done routine attempts to connect (check messages) or download data during this time (auto-download when scrolling). While this should not have caused an error, it is simply a data point to note.

Since I'm getting this error on a device as well, here is my status report:

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2025-03-29 21:08:34 +0100 (Sat, 29 Mar 2025)
Revision:19369
Build-Date:2025-03-30 01:30:37
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (19369 en) Windows 11 64-Bit
OS Build number: Windows 10 Home 24H2 (26100)
Memory Usage: 252 MB / 7972 MB (51 MB allocated, but free)
Java version: 21.0.6+8-LTS-188, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel
Screen: \Display0 2560x1440x32bpp@165Hz (scaling 1.00×1.00)
Maximum Screen Size: 2560×1440
Best cursor sizes: 16×16→32×32, 32×32→32×32
System property file.encoding: UTF-8
System property sun.jnu.encoding: Cp1252
Locale info: en_US
Numbers with default locale: 1234567890 -> 1234567890

Plugins:
+ Create_grid_of_ways (36413)
+ FastDraw (36413)
+ PicLayer (266)
+ buildings_tools (36413)
+ gridify (1743579163)
+ importvec (36413)
+ measurement (36413)
+ reverter (36413)
+ splinex (36415)
+ utilsplugin2 (36413)

Last errors/warnings:
- 00000.322 W: extended font config - overriding 'filename.Malgun_Gothic=malgun.ttf' with 'MALGUN.TTF'
- 00000.323 W: extended font config - overriding 'filename.Myanmar_Text=mmrtext.ttf' with 'MMRTEXT.TTF'
- 00000.324 W: extended font config - overriding 'filename.Mongolian_Baiti=monbaiti.ttf' with 'MONBAITI.TTF'
- 00021.217 W: java.net.SocketTimeoutException: Connect timed out
- 00021.217 E: java.net.SocketTimeoutException: Connect timed out
- 00021.217 W: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: java.net.SocketTimeoutException: Connect timed out

OSM API: https://opengeofiction.net/api/

[stoecker]

The server is broken. It announces these 2 IPs:

opengeofiction.net has address 45.33.61.238
opengeofiction.net has IPv6 address 2600:3c01::f03c:91ff:fe76:2887

but it answers only on the IPv4 address.

Contact the server admins. They should either remove the non-working IPv6 address or fix it.

[laoshubaby]

Try this endpoint ​https://api4.opengeofiction.net/api

as @wangi said in ​discord