Cryptic Error Pop-up Message: ResponseCode= 525

[grzegorz.piwonski@…]

What steps will reproduce the problem?

1. Run an instance of JOSM
2. The error will occur seemingly at random. It does not appear to be triggered by user actions.

What is the expected result?

The Pop-up message describes the error, and instructs the user on what steps to take when they encounter it.

What happens instead?

The error ID is displayed.

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

Revision:19128
Build-Date:2024-07-06 10:12:45

Identification: JOSM/1.5 (19128 en_GB) Windows 10 64-Bit
OS Build number: Windows 10 Home 22H2 (19045)
Memory Usage: 675 MB / 2026 MB (32 MB allocated, but free)
Java version: 21.0.3+9-LTS, Azul Systems, Inc., OpenJDK 64-Bit Server VM
Look and Feel: com.formdev.flatlaf.FlatDarkLaf
Screen: \Display0 1920x1080x32bpp@60Hz (scaling 1.00×1.00)
Maximum Screen Size: 1920×1080
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_GB
Numbers with default locale: 1234567890 -> 1234567890
VM arguments: [-Djpackage.app-version=1.5.19128, --add-modules=java.scripting,java.sql,javafx.controls,javafx.media,javafx.swing,javafx.web, --add-exports=java.base/sun.security.action=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-opens=java.base/java.nio=ALL-UNNAMED, --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED, --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED, --add-opens=java.desktop/javax.imageio.spi=ALL-UNNAMED, --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED, --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED, -Djpackage.app-path=%UserProfile%\AppData\Local\JOSM\JOSM.exe]
Dataset consistency test: No problems found

Plugins:
+ BuildingGeneralization (36)
+ CADTools (1008)
+ FastDraw (36226)
+ ImproveWay (32)
+ MakeParallel (v1.1.0)
+ Mapillary (2.2.4)
+ PerpendicularWayFromNode (1.0.0)
+ PolygonCutOut (v0.7.3)
+ Review.Changes (1.1.1)
+ ShapeTools (1250)
+ SimplifyArea (36209)
+ alignways (36205)
+ apache-commons (36273)
+ auto_tools (81)
+ buildings_tools (36226)
+ centernode (v1.0.4)
+ changeset-viewer (0.0.7)
+ changessum (v0.1.1)
+ contourmerge (v0.2.1)
+ flatlaf (36176)
+ gpsblam (36196)
+ graphview (36258)
+ gridify (1718663815)
+ imagery_offset_db (36289)
+ mapathoner (1.5.5)
+ mapwithai (829)
+ markseen (14)
+ measurement (36256)
+ pmtiles (36219)
+ reltoolbox (36280)
+ reverter (36256)
+ shrinkwrap (v1.1.3)
+ splinex (36126)
+ tageditor (36258)
+ terracer (36205)
+ todo (137)
+ tofix (490)
+ uberterracer (1718729454)
+ undelete (36226)
+ utilsplugin2 (36241)
+ waydownloader (36196)

Map paint styles:
- https://josm.openstreetmap.de/josmfile?page=Styles/MapWithAI&zip=1
- https://github.com/MissingMaps/josm_styles/archive/master.zip
+ https://github.com/osmlab/appledata/archive/josm_paint_inline_validation.zip
- https://josm.openstreetmap.de/josmfile?page=Styles/ModifiedHighways&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Styles/LayerChecker&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/NewHighwayColors&zip=1
+ https://gitlab.com/peculiar-theater/mapcss/-/raw/main/tm-taskgrid/tm-taskgrid.mapcss

Last errors/warnings:
- 00002.342 W: extended font config - overriding 'filename.Malgun_Gothic=malgun.ttf' with 'MALGUN.TTF'
- 00002.366 W: extended font config - overriding 'filename.Myanmar_Text=mmrtext.ttf' with 'MMRTEXT.TTF'
- 00002.367 W: extended font config - overriding 'filename.Mongolian_Baiti=monbaiti.ttf' with 'MONBAITI.TTF'
- 00009.983 E: java.security.KeyStoreException: Windows-ROOT not found. Cause: java.security.NoSuchAlgorithmException: Windows-ROOT KeyStore not available
- 03962.799 E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=525
- 03962.815 E: Communication with OSM server failed - ResponseCode=525

[anonymous]

Error 525 Pop-up Window

[stoecker]

What did you do before the error came? You have a lot of plugins installed, I assume that error comes from one of the plugins (e.g. waydownloader) which also explains why there is no further error description.

Probably 525 is a TLS handshake error which could indicate network issues. As JOSM itself doesn't permanently contact the API it's very likely a plugin.

You could start the version of JOSM showing the console, so you see which request goes out and fails. That would help to find the origin of the request. Another approach would be to disable the plugins one-by-one until the error vanishes.

[GerdP]

I think JOSM performs some scheduled network tasks, e.g. it checks if the user has new mail in the OSM postbox. I think it also asks for open changesets regularly. I think the OSM server was attacked today and yesterday (DDOS attacks) and I also saw random popups with strange content but didn't care to find out more.

[Grzegorz]

Replying to stoecker:

What did you do before the error came? You have a lot of plugins installed, I assume that error comes from one of the plugins (e.g. waydownloader) which also explains why there is no further error description.

Not much, really. I hadn't actually used any of the plug-ins, besides buildings_tools. I was taking a break, and when I came back I saw the error. There may have been some edited elements i.e I had made changes that I hadn't yet uploaded.

Probably 525 is a TLS handshake error which could indicate network issues. As JOSM itself doesn't permanently contact the API it's very likely a plugin.

You could start the version of JOSM showing the console, so you see which request goes out and fails. That would help to find the origin of the request. Another approach would be to disable the plugins one-by-one until the error vanishes.

The error was transient, and I don't know how to recreate it: I did not need to restart JOSM, (or anything like that) to be able to continue editing and uploading data to OSM. How would I go about using the console method? I think it's the better option in this case.

This is the kind of information that would be good to include in the warning message, so that users are more likely to identify the cause before submiting a ticket.

[stoecker]

Well, JOSM does describe common error messages. But 525 is not common. I have never seen it before. A DOS attack probably could explain it. I don't think we can do much in this case. Let's hope it is really temporary. If new information comes up, please add it and reopen the ticket.