"There was an error deleting that topic. Please contact the site's administrator"

I recently followed the instructions here to enable permanent delete: Introducing permanently delete post functionality

I can now see the “Permanently Delete” option

However, when I try to delete the topic I get the following notification:

image

/logs gives me the following:
image

net-http-0.2.2/lib/net/http/response.rb:142:in `error!'
net-http-0.2.2/lib/net/http/response.rb:151:in `value'
net-http-0.2.2/lib/net/http.rb:1039:in `connect'
net-http-0.2.2/lib/net/http.rb:995:in `do_start'
net-http-0.2.2/lib/net/http.rb:984:in `start'
net-http-0.2.2/lib/net/http.rb:1570:in `request'
rack-mini-profiler-3.0.0/lib/patches/net_patches.rb:19:in `block in request_with_mini_profiler'
rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:46:in `step'
rack-mini-profiler-3.0.0/lib/patches/net_patches.rb:18:in `request_with_mini_profiler'
net-http-0.2.2/lib/net/http.rb:1480:in `request_get'
fastimage-2.2.6/lib/fastimage.rb:296:in `fetch_using_http_from_parsed_uri'
fastimage-2.2.6/lib/fastimage.rb:278:in `fetch_using_http'
fastimage-2.2.6/lib/fastimage.rb:244:in `initialize'
fastimage-2.2.6/lib/fastimage.rb:140:in `new'
fastimage-2.2.6/lib/fastimage.rb:140:in `size'
/var/www/discourse/lib/cooked_processor_mixin.rb:186:in `get_size'
/var/www/discourse/lib/cooked_post_processor.rb:158:in `convert_to_link!'
/var/www/discourse/lib/cooked_post_processor.rb:369:in `block in post_process_images'
nokogiri-1.13.8-x86_64-linux/lib/nokogiri/xml/node_set.rb:234:in `block in each'
nokogiri-1.13.8-x86_64-linux/lib/nokogiri/xml/node_set.rb:233:in `upto'
nokogiri-1.13.8-x86_64-linux/lib/nokogiri/xml/node_set.rb:233:in `each'
/var/www/discourse/lib/cooked_post_processor.rb:367:in `post_process_images'
/var/www/discourse/lib/cooked_post_processor.rb:44:in `block in post_process'
/var/www/discourse/lib/distributed_mutex.rb:57:in `block in synchronize'
/var/www/discourse/lib/distributed_mutex.rb:53:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:53:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:38:in `synchronize'
/var/www/discourse/lib/cooked_post_processor.rb:40:in `post_process'
/var/www/discourse/app/jobs/regular/process_post.rb:26:in `block in execute'
/var/www/discourse/lib/distributed_mutex.rb:57:in `block in synchronize'
/var/www/discourse/lib/distributed_mutex.rb:53:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:53:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:38:in `synchronize'
/var/www/discourse/app/jobs/regular/process_post.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:237:in `block (2 levels) in perform'
rails_multisite-4.0.1/lib/rails_multisite/connection_management.rb:80:in `with_connection'
/var/www/discourse/app/jobs/base.rb:226:in `block in perform'
/var/www/discourse/app/jobs/base.rb:222:in `each'
/var/www/discourse/app/jobs/base.rb:222:in `perform'
sidekiq-6.5.6/lib/sidekiq/processor.rb:202:in `execute_job'
sidekiq-6.5.6/lib/sidekiq/processor.rb:170:in `block (2 levels) in process'
sidekiq-6.5.6/lib/sidekiq/middleware/chain.rb:177:in `block in invoke'
/var/www/discourse/lib/sidekiq/pausable.rb:138:in `call'
sidekiq-6.5.6/lib/sidekiq/middleware/chain.rb:179:in `block in invoke'
sidekiq-6.5.6/lib/sidekiq/middleware/chain.rb:182:in `invoke'
sidekiq-6.5.6/lib/sidekiq/processor.rb:169:in `block in process'
sidekiq-6.5.6/lib/sidekiq/processor.rb:136:in `block (6 levels) in dispatch'
sidekiq-6.5.6/lib/sidekiq/job_retry.rb:113:in `local'
sidekiq-6.5.6/lib/sidekiq/processor.rb:135:in `block (5 levels) in dispatch'
sidekiq-6.5.6/lib/sidekiq.rb:44:in `block in <module:Sidekiq>'
sidekiq-6.5.6/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'
sidekiq-6.5.6/lib/sidekiq/processor.rb:263:in `stats'
sidekiq-6.5.6/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'
sidekiq-6.5.6/lib/sidekiq/job_logger.rb:13:in `call'
sidekiq-6.5.6/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'
sidekiq-6.5.6/lib/sidekiq/job_retry.rb:80:in `global'
sidekiq-6.5.6/lib/sidekiq/processor.rb:124:in `block in dispatch'
sidekiq-6.5.6/lib/sidekiq/job_logger.rb:39:in `prepare'
sidekiq-6.5.6/lib/sidekiq/processor.rb:123:in `dispatch'
sidekiq-6.5.6/lib/sidekiq/processor.rb:168:in `process'
sidekiq-6.5.6/lib/sidekiq/processor.rb:78:in `process_one'
sidekiq-6.5.6/lib/sidekiq/processor.rb:68:in `run'
sidekiq-6.5.6/lib/sidekiq/component.rb:8:in `watchdog'
sidekiq-6.5.6/lib/sidekiq/component.rb:17:in `block in safe_thread'

I’ve had 502 errors for a few things in this instance, which has prevented features like lightboxing. The 502 is presumably due to our VPN, self-published certificates or proxy.

However, I’m confused as to why the permanent delete functionality would suffer from those issues. I understood it was just a direct write to the database, similar to posting a topic etc(which is fully functional).

Has anyone experienced anything similar?