[bug] Reports that no base_url is set for uploads, won't start

alster commented

2024-05-23 06:23:14 +00:00

Your setup

OTP

Extra details

Debian Bookworm, latest upgrades, Apache2 as Proxy

Version

2024.04.1, 3.13.2

PostgreSQL version

13

What were you trying to do?

Starting the instance after upgrading to the newest release.

What did you expect to happen?

Smooth startup of the instance, maybe a warning in the release notes, that this will break instances NOT using an extra set base_url for uploads.
It's on the same, singleuser, machine, the data just hit's the same instance and database either way.

What did I try to recover?

Since there's no description of a way for downgrading and I do not know if it'd be enough to just overwrite the current working folder with the older version I did not ttry that.
I did try to poke the database for the base_url, but didn't find any useful or human readable contents to change the base_url for proxying (or even turning it off).
Also migrating the database-config to file does not work, because RPC calls aren't possible if it's not running.

What actually happened?

No startup.

Logs

May 23 08:00:31 v2202104145055148180 pleroma[626200]: 08:00:31.439 [notice] Application pleroma exited: exited in: Pleroma.Application.start(:normal, [])
May 23 08:00:31 v2202104145055148180 pleroma[626200]:     ** (EXIT) an exception was raised:
May 23 08:00:31 v2202104145055148180 pleroma[626200]:         ** (ArgumentError) No base_url set for uploads - please set one in your config!
May 23 08:00:31 v2202104145055148180 pleroma[626200]:             (pleroma 3.13.2-0-g050bc74) lib/pleroma/config/deprecation_warnings.ex:398: Pleroma.Config.DeprecationWarnings.check_uploader_base_url_set/0
May 23 08:00:31 v2202104145055148180 pleroma[626200]:             (pleroma 3.13.2-0-g050bc74) lib/pleroma/config/deprecation_warnings.ex:223: Pleroma.Config.DeprecationWarnings.warn/0
May 23 08:00:31 v2202104145055148180 pleroma[626200]:             (pleroma 3.13.2-0-g050bc74) lib/pleroma/application.ex:53: Pleroma.Application.start/2
May 23 08:00:31 v2202104145055148180 pleroma[626200]:             (kernel 9.0.2) application_master.erl:293: :application_master.start_it_old/4
May 23 08:00:31 v2202104145055148180 pleroma[626200]: 08:00:31.444 [notice]     :alarm_handler: {:clear, :system_memory_high_watermark}
May 23 08:00:32 v2202104145055148180 pleroma[626200]: Kernel pid terminated (application_controller) ({application_start_failure,pleroma,{bad_return,{{'Elixir.Pleroma.Application',start,[normal,[]]},{'EXIT',{#{message => <<"No base_url set for uploads - please set one in your conf>
May 23 08:00:32 v2202104145055148180 pleroma[626200]:

Severity

I cannot use the software

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Your setup OTP ### Extra details Debian Bookworm, latest upgrades, Apache2 as Proxy ### Version 2024.04.1, 3.13.2 ### PostgreSQL version 13 ### What were you trying to do? Starting the instance after upgrading to the newest release. ### What did you expect to happen? Smooth startup of the instance, maybe a warning in the release notes, that this will break instances NOT using an extra set base_url for uploads. It's on the same, singleuser, machine, the data just hit's the same instance and database either way. ### What did I try to recover? Since there's no description of a way for downgrading and I do not know if it'd be enough to just overwrite the current working folder with the older version I did not ttry that. I did try to poke the database for the base_url, but didn't find any useful or human readable contents to change the base_url for proxying (or even turning it off). Also migrating the database-config to file does not work, because RPC calls aren't possible if it's not running. ### What actually happened? No startup. ### Logs ```shell May 23 08:00:31 v2202104145055148180 pleroma[626200]: 08:00:31.439 [notice] Application pleroma exited: exited in: Pleroma.Application.start(:normal, []) May 23 08:00:31 v2202104145055148180 pleroma[626200]: ** (EXIT) an exception was raised: May 23 08:00:31 v2202104145055148180 pleroma[626200]: ** (ArgumentError) No base_url set for uploads - please set one in your config! May 23 08:00:31 v2202104145055148180 pleroma[626200]: (pleroma 3.13.2-0-g050bc74) lib/pleroma/config/deprecation_warnings.ex:398: Pleroma.Config.DeprecationWarnings.check_uploader_base_url_set/0 May 23 08:00:31 v2202104145055148180 pleroma[626200]: (pleroma 3.13.2-0-g050bc74) lib/pleroma/config/deprecation_warnings.ex:223: Pleroma.Config.DeprecationWarnings.warn/0 May 23 08:00:31 v2202104145055148180 pleroma[626200]: (pleroma 3.13.2-0-g050bc74) lib/pleroma/application.ex:53: Pleroma.Application.start/2 May 23 08:00:31 v2202104145055148180 pleroma[626200]: (kernel 9.0.2) application_master.erl:293: :application_master.start_it_old/4 May 23 08:00:31 v2202104145055148180 pleroma[626200]: 08:00:31.444 [notice] :alarm_handler: {:clear, :system_memory_high_watermark} May 23 08:00:32 v2202104145055148180 pleroma[626200]: Kernel pid terminated (application_controller) ({application_start_failure,pleroma,{bad_return,{{'Elixir.Pleroma.Application',start,[normal,[]]},{'EXIT',{#{message => <<"No base_url set for uploads - please set one in your conf> May 23 08:00:32 v2202104145055148180 pleroma[626200]: ``` ### Severity I cannot use the software ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.

alster added the

bug

label 2024-05-23 06:23:14 +00:00

floatingghost commented

2024-05-23 09:13:25 +00:00

Owner

this was mentioned in all release notes and posts as something you must set now

https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/CHANGELOG.md#changed-1

https://meta.akkoma.dev/t/akkoma-stable-2024-03-securer-i-barely-know-her/681#explicit-upload-and-media-proxy-domains-5

please ensure that in future you check upgrade notes to see if there are any breaking changes that require your attention

this was mentioned in all release notes and posts as something you must set now https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/CHANGELOG.md#changed-1 https://meta.akkoma.dev/t/akkoma-stable-2024-03-securer-i-barely-know-her/681#explicit-upload-and-media-proxy-domains-5 please ensure that in future you check upgrade notes to see if there are any breaking changes that require your attention

floatingghost closed this issue

2024-05-23 09:13:25 +00:00

alster commented

2024-05-23 09:18:21 +00:00

Author

Not for 3.13.2.
Also there's nothing at: https://akkoma.dev/AkkomaGang/akkoma/releases/tag/v3.13.2
(Which, until now was my only source to be notified of new releases.)

Also with the 3.13.1 release there where no issues, as I reverted back from that dual wielding domains and instances just for media from the quick fix before that.

Also it worked perfectly fine without the cache.* domain and just using the plain domain like before and it looks like this did overwrite these settings.

Not for 3.13.2. Also there's nothing at: https://akkoma.dev/AkkomaGang/akkoma/releases/tag/v3.13.2 (Which, until now was my only source to be notified of new releases.) Also with the 3.13.1 release there where no issues, as I reverted back from that dual wielding domains and instances just for media from the quick fix before that. Also it worked perfectly fine without the cache.* domain and just using the plain domain like before and it looks like this did overwrite these settings.

floatingghost commented

2024-05-23 09:20:21 +00:00

Owner

it did not change in this release, it was a release prior

it did not change in this release, it was a release _prior_

floatingghost commented

2024-05-23 09:20:38 +00:00

Owner

wait, actually TWO releases prior

wait, actually _TWO_ releases prior

👍 1

alster commented

2024-05-23 09:33:06 +00:00

Author

And yet it worked perfectly fine until this release. Otherwise I may have even changed that, now I'm trying to get this settings right in postgresql and learning to use that by doing so.

floatingghost commented

2024-05-23 09:35:14 +00:00

Owner

you can check the source code if you'd like, nothing regarding this has changed in over two months

you don't need to do anything in the database, the meta link tells you exactly what you're supposed to do

you can check the source code if you'd like, nothing regarding this has changed in over two months you don't need to do anything in the database, the meta link tells you exactly what you're supposed to do

alster commented

2024-05-23 09:44:36 +00:00

Author

you don't need to do anything in the database, the meta link tells you exactly what you're supposed to do
Then that's on me, since I thought so after moving the config to the database in the first place.

And this is the hint that whould've been nice at the changelog, that made it blow up, somewhere in the comments.
https://meta.akkoma.dev/t/akkoma-stable-2024-03-securer-i-barely-know-her/681/12

> you don't need to do anything in the database, the meta link tells you exactly what you're supposed to do Then that's on me, since I thought so after moving the config to the database in the first place. And this is the hint that whould've been nice at the changelog, that made it blow up, somewhere in the comments. https://meta.akkoma.dev/t/akkoma-stable-2024-03-securer-i-barely-know-her/681/12

alster commented

2024-05-23 09:53:25 +00:00

Author

It's working now, thanks for hitting me to the right things. :)

[bug] Reports that no base_url is set for uploads, won't start #781

Your setup

Extra details

Version

PostgreSQL version

What were you trying to do?

What did you expect to happen?

What did I try to recover?

What actually happened?

Logs

Severity

Have you searched for this issue?