Skip to content
Discussion options

You must be logged in to vote

Thanks for the follow-up — I found the actual cause, and it wasn't the missing property.

phoss-SMP creates the Directory client once at startup and keeps it in memory. When you change
the Directory URL in the UI, the new value is stored correctly in the database — but on the SQL
backend the running instance was not told about the change, so it kept talking to the old URL
(the one with /public), which is why you still got the 405.

Adding the property to application.properties made you restart the container, and that restart
picked up the corrected URL. So the restart fixed it, not the property.

This is fixed for v8.1.8 — changing the SMP settings now takes effect immediately, without a
res…

Replies: 2 comments 11 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
11 replies
@nabil-mokhtar
Comment options

@nabil-mokhtar
Comment options

@phax
Comment options

phax Aug 6, 2026
Maintainer

@phax
Comment options

phax Aug 6, 2026
Maintainer

Answer selected by nabil-mokhtar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants