The certificates guide sent a description when it added a Let's Encrypt account. The server sets that itself and refuses it ("Cannot modify server set property"), so on the 2026 series the guide only worked where a matching account already existed. Same fix as 114ad2c on main (27.1-rc.8).
Reported in forum topic 279.
The certificates guide sent a description when it added a Let's Encrypt account. The server sets that itself and refuses it ("Cannot modify server set property"), so on the 2026 series the guide only worked where a matching account already existed. Same fix as 114ad2c on main (27.1-rc.8).
Reported in forum topic 279.
The server writes an ACME provider's description itself and refuses one
from a client ("Cannot modify server set property"), so the guide could
never add a Let's Encrypt account: it only worked on servers that already
had one with the right challenge type. The same fix as 114ad2c on main.
Reported in forum topic 279.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The certificates guide sent a description when it added a Let's Encrypt account. The server sets that itself and refuses it ("Cannot modify server set property"), so on the 2026 series the guide only worked where a matching account already existed. Same fix as
114ad2con main (27.1-rc.8).Reported in forum topic 279.
The server writes an ACME provider's description itself and refuses one from a client ("Cannot modify server set property"), so the guide could never add a Let's Encrypt account: it only worked on servers that already had one with the right challenge type. The same fix as114ad2con main. Reported in forum topic 279.