图片上传现在导致链接失效

New issue now, cannot upload, I only tried images, tried jpg and webp, just shows broken link. Tried png and can see it momentarily, then immediate broken link. Any thoughts on this issue? It must have started quite recently. I can upload pdf’s however. (The existing older images all seem to be okay, still showing appropriately)

image

image349×187 2.66 KB

Earlier this morning I tried to upgrade via gui, then only has white screen, so tried cli, same thing, sp I restored from a very recent snapshot. I am not sure if that is part of this problem or not, I probably upload images a week ago, without issue.

Does it also happen when using Markdown mode (toggling from A to M :down_arrow:)?

Can you check if there are any errors on your browser console output?

What commit version is your instance on?

Can you inspect this broken element and see how’s the HTML?

Updating should work, so that indeed may be part of the problem.

2 个赞

Glad i thought of bunny. Resolved, updated maxmind country block whacked bunny’s access. This may be same issue with the white screen update. I can’t try that again until Saturday.

30 minutes ago:

Same issue in Markdown.

Discourse v3.6.0.beta2-latest — — Ember v6.6.0deprecated.js:62 [THEME 23 ‘Inline PDF Previews’] Deprecation notice: Accessing site.mobileView or site.desktopView during the site initialization can lead to errors and inconsistencies when the browser window is resized. Please move these checks to a component, transformer, or API callback that executes during page rendering. [deprecated since Discourse 3.5.0.beta9-dev] [deprecation id: discourse.static-viewport-initialization] [info: ]a @ deprecated.js:62get mobileView @ site.js:124(anonymous) @ compat.js:22X @ index.js:416(anonymous) @ compat.js:21(anonymous) @ initialize-for-pdf-preview.js:10eQ @ plugin-api.gjs:3485initialize @ initialize-for-pdf-preview.js:9(anonymous) @ app.js:239(anonymous) @ index.js:379e.each @ index.js:183e.walk @ index.js:112e.each @ index.js:59e.topsort @ index.js:65_runInitializer @ index.js:392runInstanceInitializers @ index.js:377_bootSync @ instance.js:116didBecomeReady @ index.js:784invoke @ index.js:262flush @ index.js:180flush @ index.js:334_end @ index.js:762(anonymous) @ index.js:499Promise.then(anonymous) @ index.js:18flush @ index.js:29_scheduleAutorun @ index.js:928_ensureInstance @ index.js:919schedule @ index.js:618f @ index.js:343waitForDOMReady @ index.js:512init @ index.js:412_ @ core.js:97create @ core.js:599(anonymous) @ start-app.js:8await in (anonymous)(anonymous) @ discourse-boot.js:13(anonymous) @ discourse-boot.js:1Understand this warningsite.js:217 ✅ Using the new ‘glimmer’ post stream!content-script-vimeo.js:11 log-init[Violation] Potential permissions policy violation: fullscreen is not allowed in this document.

Deprecation notice: Setting timezone property of user object is deprecated. Use user_option object instead [deprecated since Discourse 2.9.0.beta12] [removal in Discourse 3.0.0.beta1] [deprecation id: discourse.user.userOptions]

I am not sure what I am looking for when I inspect the broken link, in terms of the html.

Not to muddy the waters, but I just remembered I use bunny.net for cdn, if that could matter, but I have never had any issue with them in well over a year and actually forgot I use them.

1 个赞