yunohost-apps/gotosocial_ynh

GoToSocial package for YunoHost: an ActivityPub social network server, written in Golang.

GoToSocial for YunoHost

Read this README in other languages.

This package allows you to install GoToSocial quickly and simply on a YunoHost server.
If you don't have YunoHost, please consult the guide to learn how to install it.

Overview

GoToSocial is a fast ActivityPub social network server, written in Golang.

With GoToSocial, you can keep in touch with your friends, post, read, and share images and articles. All without being tracked or advertised to!

The official documentation is at docs.gotosocial.org.
The documentation for this YunoHost package can be read here and the admin is strongly encouraged to read it!

Please note that this package uses the "i'm so tired" software license 1.0, please read it and accept it before proceeding with installation.

Shipped version: 0.15.0~ynh2

Screenshots

🔴 Antifeatures

• Alpha software: Early development stage. May contain changing or unstable features, bugs, and security vulnerability.
• Not totally free package: The YunoHost package of this app is under an overall free licence, but with clauses that restrict its use.

Documentation and resources

• Official app website: https://gotosocial.org/
• Official user documentation: https://docs.gotosocial.org/en/latest/
• Official admin documentation: https://docs.gotosocial.org/en/latest/
• Upstream app code repository: https://github.com/superseriousbusiness/gotosocial
• YunoHost Store: https://apps.yunohost.org/app/gotosocial
• Report a bug: https://github.com/YunoHost-Apps/gotosocial_ynh/issues

Developer info

Please send your pull request to the testing branch.

To try the testing branch, please proceed like that:

sudo yunohost app install https://github.com/YunoHost-Apps/gotosocial_ynh/tree/testing --debug
or
sudo yunohost app upgrade gotosocial -u https://github.com/YunoHost-Apps/gotosocial_ynh/tree/testing --debug

More info regarding app packaging: https://yunohost.org/packaging_apps

gotosocial_ynh's Issues

Can't install on ARM system

Due to the actual helper for detecting the system architecture, which does not differentiate armv6 and armv7 (only arm) and because gotosocial provides different binaries for those 2 architectures, this package cannot be installed on armv6 or armv7 architectures

Installation fails

Describe the bug

The installation process fails

Context

• Hardware: VPS bought online
• YunoHost version: 11.0.10.2
• I have access to my server: Through SSH
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no

Steps to reproduce

• launched the install from the web interface

Expected behavior

The app should be installed successfully

Logs

Here is the installation log

Unexpected token < on JSON

Describe the bug

some changes on web admin panel are not saved.

Context

• Hardware: Raspberry Pi
• YunoHost version: 463 latest stable
• I have access to my server: *Through SSH | through the webadmin *
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• latest 0.3.6 gotosocial

Steps to reproduce

• log in as admin in /admin panel
• edit "description" field (actually any, as I've tried with "short description" an "email" fields)
• click save button
• changes are not saved and I get this info

Expected behavior

changes are saved to config.yaml (or where changes belong)

Logs

I don't see anything about this issue in /var/log/gotosocial/gotosocial.log

I could upload a blocked instances list though.

Many thanks

Asking help for NGINX 404 rule

related to #86 , I'm not askin for help on #86

I would like to set a default image to load in old posts (that actually nobody would never be interested in, but that's not an issue 😄 ) that are not correctly linked so any possible user would get an image that says that the image is lost, so not their/my fault (shit happens! 😸 ). Eventually I will adventure to delete broken link images from server so I free some space in the server (small VPS)

Back to topic:

So instead a 404 server error for the image, the server would load a default image. Reference: https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/#check-if-file-exists

I've tried adding to /etc/nginx/conf.d/gts.domain.tld.d/gotosocial.conf this code

location /fileserver {
  try_files $uri /fileserver/default.jpg;
}

also tried with fileserver, without /

I have upload default.jpg to /home/yunohost.app/gotosocial/ and set ownership to gotosocial:gotosocial (as the other files/folders in that folder)

because I see that image files are server from gts.domain.tld/fileserver , but it does not work. Should I add this rule to gts.domain.tld.conf (main config file) or have I set wrong location in the config?

Any hint would be valuable. Where should I set this rule without breaking nginx/gotosocial config? Thank you.

Configuration panel

It would be nice to have a configuration panel
For exemple to create new user for the gotosocial instance without using cli (because gotosocial haven't an admin panel that provides this kind of action)

Expose `account-domain` setting with suitable warnings

Hey, thanks for packaging this.

I can take a crack at this one myself in the coming weeks, but I don't have a YNH test environment set up under Windows, and it seems simple enough for anyone who already has somewhere to test changes while developing.

I'd like to expose the following setting:

# String. Domain to use when federating profiles. This is useful when you want your server to be at                                                                       
# eg., "gts.example.org", but you want the domain on accounts to be "example.org" because it looks better                                                                 
# or is just shorter/easier to remember.                                             
#                                                                                    
# To make this setting work properly, you need to redirect requests at "example.org/.well-known/webfinger"                                                                
# to "gts.example.org/.well-known/webfinger" so that GtS can handle them properly.   
#                                                                                    
# You should also redirect requests at "example.org/.well-known/nodeinfo" in the same way.                                                                                
# An empty string (ie., not set) means that the same value as 'host' will be used.   
#                                                                                    
# DO NOT change this after your server has already run once, or you will break things!                                                                                    
#                                                                                    
# Examples: ["example.org","server.com"]                                             
#                                                                                    
# Please read the appropriate section of the installation guide before you go messing around with this setting:                                                           
# https://docs.gotosocial.org/installation_guide/advanced/#can-i-host-my-instance-at-fediexampleorg-but-have-just-exampleorg-in-my-username                               
#                                                                                    
# Default: ""                                                                        
account-domain: ""                                                                   

Right now I have a few custom Nginx configurations partially redirecting my main YNH-hosted domain to a remote Friendica instance, using the above redirected paths, but Friendica doesn't let me specify a canonical profile domain. It would be great if this option was exposed to YNH, with suitable warning text telling folks they're on their own for managing whatever domain redirects they set up. I'm happy with it just being a string, and if possible, including the links to the installation guide so installers know what they're getting into.

I think it's important because it looks like it can't/shouldn't be changed after installation. So even if I wanted to change it, once the app is installed it's too late.

Thanks again. Happy to test any changes on my production instance, I just don't have anything set up for development.

postgresql is dead after installing gotosocial

Describe the bug

not a bug in the app itself, but in relation to it since i started getting Service postgresql is dead :( after every diagnosis.

Context

• Hardware: VPS bought online ( Contabo )
• YunoHost version: 11.0.9.15 (stable)
• I have access to my server: Through SSH | through the webadmin
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• Using, or trying to install package version/branch: 0.5.1~ynh1

Steps to reproduce

1. install gotosocial
2. run diagnosis

Expected behavior

not having a ded postgresql?

Logs

sudo yunohost service log postgresql
/var/log/postgresql/postgresql-13-main.log: 
  - 2022-10-01 08:55:26.369 CEST [135976] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:26.369 CEST [135976] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, PMWEwHRbOpwllkWcCmpuyxpz) already exists.
  - 2022-10-01 08:55:26.369 CEST [135976] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'PMWEwHRbOpwllkWcCmpuyxpz', 'image/jpeg', 20355, 1664607326368, 'IMG_20210416_084346_e_1618555512898.jpg', 'gVbrlIuVnZymGWNTNsKQivSx', 1664607326368)
  - 2022-10-01 08:55:26.438 CEST [135983] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:26.438 CEST [135983] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, PMWEwHRbOpwllkWcCmpuyxpz) already exists.
  - 2022-10-01 08:55:26.438 CEST [135983] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'PMWEwHRbOpwllkWcCmpuyxpz', 'image/jpeg', 20355, 1664607326434, 'IMG_20210416_084346_e_1618555512898.jpg', 'tkiFmKmHDsLoXHAuzALrRVxO', 1664607326434)
  - 2022-10-01 08:55:26.515 CEST [135974] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:26.515 CEST [135974] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, PMWEwHRbOpwllkWcCmpuyxpz) already exists.
  - 2022-10-01 08:55:26.515 CEST [135974] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'PMWEwHRbOpwllkWcCmpuyxpz', 'image/jpeg', 20355, 1664607326515, 'IMG_20210416_084346_e_1618555512898.jpg', 'sDjyCWMRVMosIOvuITvQoSxZ', 1664607326515)
  - 2022-10-01 08:55:27.236 CEST [135943] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.236 CEST [135943] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, PMWEwHRbOpwllkWcCmpuyxpz) already exists.
  - 2022-10-01 08:55:27.236 CEST [135943] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'PMWEwHRbOpwllkWcCmpuyxpz', 'image/jpeg', 20355, 1664607327235, 'IMG_20210416_084346_e_1618555512898.jpg', 'ITgKCCKYsAomsrAYbzvzfPaS', 1664607327235)
  - 2022-10-01 08:55:27.333 CEST [135940] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.333 CEST [135940] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, PMWEwHRbOpwllkWcCmpuyxpz) already exists.
  - 2022-10-01 08:55:27.333 CEST [135940] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'PMWEwHRbOpwllkWcCmpuyxpz', 'image/jpeg', 20355, 1664607327332, 'IMG_20210416_084346_e_1618555512898.jpg', 'jALxDoeHLECPRNTqIezVpxjM', 1664607327332)
  - 2022-10-01 08:55:27.343 CEST [135943] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.343 CEST [135943] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(semi.social, HVykjHcfdtlQfBcqfMimMlIp) already exists.
  - 2022-10-01 08:55:27.343 CEST [135943] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('semi.social', 'HVykjHcfdtlQfBcqfMimMlIp', 'image/png', 1411740, 1664607327342, 'Pixel Oliver - Medusa.png', 'pALKLczonRWiJzKXQXJDEbXE', 1664607327342)
  - 2022-10-01 08:55:27.392 CEST [135943] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.392 CEST [135943] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, PMWEwHRbOpwllkWcCmpuyxpz) already exists.
  - 2022-10-01 08:55:27.392 CEST [135943] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'PMWEwHRbOpwllkWcCmpuyxpz', 'image/jpeg', 20355, 1664607327391, 'IMG_20210416_084346_e_1618555512898.jpg', 'EfatNrIvwplpvECJjdRazOkD', 1664607327391)
  - 2022-10-01 08:55:27.462 CEST [135945] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.462 CEST [135945] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, PMWEwHRbOpwllkWcCmpuyxpz) already exists.
  - 2022-10-01 08:55:27.462 CEST [135945] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'PMWEwHRbOpwllkWcCmpuyxpz', 'image/jpeg', 20355, 1664607327460, 'IMG_20210416_084346_e_1618555512898.jpg', 'NDqgXMNRdYSTuMGifoiAYzkB', 1664607327460)
  - 2022-10-01 08:55:27.616 CEST [135974] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.616 CEST [135974] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(autonomic.zone, BihZxEafuxzwMOPptsQrINkn) already exists.
  - 2022-10-01 08:55:27.616 CEST [135974] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('autonomic.zone', 'BihZxEafuxzwMOPptsQrINkn', 'image/jpeg', 44976, 1664607327615, 'socialsalior.jpg', 'MpdKNBvkQcErMXJorreJAyZf', 1664607327615)
  - 2022-10-01 08:55:27.672 CEST [135945] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.672 CEST [135945] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, uMwYEJCrzFZbDpmFgUdHDnvw) already exists.
  - 2022-10-01 08:55:27.672 CEST [135945] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'uMwYEJCrzFZbDpmFgUdHDnvw', 'image/png', 311416, 1664607327671, 'puffinux_psychadelic_simple.png', 'rMjAPsMRPJlkMjchiWAIpSTG', 1664607327671)
  - 2022-10-01 08:55:27.755 CEST [135974] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.755 CEST [135974] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, tdFWvVBvBFOCvmrzcFmnlZqW) already exists.
  - 2022-10-01 08:55:27.755 CEST [135974] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'tdFWvVBvBFOCvmrzcFmnlZqW', 'image/png', 6039, 1664607327754, '280f27c808db6f39.png', 'tzrHcArabNKskQkloXhwpzlh', 1664607327754)
  - 2022-10-01 08:55:27.935 CEST [135976] matrix_synapse@matrix_synapse ERROR:  duplicate key value violates unique constraint "remote_media_cache_media_origin_media_id_key"
  - 2022-10-01 08:55:27.935 CEST [135976] matrix_synapse@matrix_synapse DETAIL:  Key (media_origin, media_id)=(matrix.org, PMWEwHRbOpwllkWcCmpuyxpz) already exists.
  - 2022-10-01 08:55:27.935 CEST [135976] matrix_synapse@matrix_synapse STATEMENT:  INSERT INTO remote_media_cache (media_origin, media_id, media_type, media_length, created_ts, upload_name, filesystem_id, last_access_ts) VALUES('matrix.org', 'PMWEwHRbOpwllkWcCmpuyxpz', 'image/jpeg', 20355, 1664607327934, 'IMG_20210416_084346_e_1618555512898.jpg', 'ejpvswMgrRaDvzaXrPMxscAQ', 1664607327934)
  - 2022-10-03 13:06:02.866 CEST [135910] LOG:  received fast shutdown request
  - 2022-10-03 13:06:02.902 CEST [135910] LOG:  aborting any active transactions
  - 2022-10-03 13:06:02.907 CEST [135910] LOG:  background worker "logical replication launcher" (PID 135917) exited with exit code 1
  - 2022-10-03 13:06:02.947 CEST [155405] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-10-03 13:06:02.947 CEST [155546] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-10-03 13:06:02.947 CEST [165989] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-10-03 13:06:02.991 CEST [135912] LOG:  shutting down
  - 2022-10-03 13:06:03.108 CEST [135910] LOG:  database system is shut down
  - 2022-10-03 13:06:03.416 CEST [211884] LOG:  starting PostgreSQL 13.8 (Debian 13.8-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  - 2022-10-03 13:06:03.417 CEST [211884] LOG:  listening on IPv6 address "::1", port 5432
  - 2022-10-03 13:06:03.417 CEST [211884] LOG:  listening on IPv4 address "127.0.0.1", port 5432
  - 2022-10-03 13:06:03.418 CEST [211884] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  - 2022-10-03 13:06:03.433 CEST [211885] LOG:  database system was shut down at 2022-10-03 13:06:03 CEST
  - 2022-10-03 13:06:03.523 CEST [211884] LOG:  database system is ready to accept connections
journalctl: 
  - -- Journal begins at Thu 2022-09-15 00:26:29 CEST, ends at Mon 2022-10-03 13:06:08 CEST. --
  - Sep 18 18:56:59 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 18 18:57:02 systemd[1]: [email protected]: Succeeded.
  - Sep 18 18:57:02 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 18 18:57:02 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 18 18:57:10 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 18 19:06:13 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 18 19:06:13 systemd[1]: [email protected]: Succeeded.
  - Sep 18 19:06:13 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 18 19:06:13 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 18 19:06:16 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 18 19:37:10 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 18 19:37:11 systemd[1]: [email protected]: Succeeded.
  - Sep 18 19:37:11 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 18 19:37:11 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 18 19:37:15 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 18 19:51:41 systemd[1]: Reloading PostgreSQL Cluster 11-main.
  - Sep 18 19:51:41 systemd[1]: Reloaded PostgreSQL Cluster 11-main.
  - -- Boot 09c6bc504c524e05bdc65fd6bd7462e3 --
  - Sep 19 18:19:12 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 19 18:19:14 postgresql@11-main[686]: Removed stale pid file.
  - Sep 19 18:19:26 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 19 18:31:26 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 19 18:31:26 systemd[1]: [email protected]: Succeeded.
  - Sep 19 18:31:26 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 19 18:31:26 systemd[1]: [email protected]: Consumed 1.937s CPU time.
  - -- Boot ee0e86dc619042259065dc271e150806 --
  - Sep 19 18:32:11 systemd[1]: Starting PostgreSQL Cluster 11-main...
  - Sep 19 18:32:20 systemd[1]: Started PostgreSQL Cluster 11-main.
  - Sep 19 18:41:56 systemd[1]: Stopping PostgreSQL Cluster 11-main...
  - Sep 19 18:41:57 systemd[1]: [email protected]: Succeeded.
  - Sep 19 18:41:57 systemd[1]: Stopped PostgreSQL Cluster 11-main.
  - Sep 19 18:41:57 systemd[1]: [email protected]: Consumed 1.559s CPU time.

Implement OpenID Connect (OIDC)

GTS supports OIDC, so it would be nice to allow YNH accounts to connect to GTS through this, with the help of dex_ynh (or maybe canaille)

docs: https://docs.gotosocial.org/en/latest/configuration/oidc/

Version 0.10.0

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.10.0

Which branch should I target (using a PR) to upgrade the package ?

Packaging V2 first ?

Version 0.8.1 released

Minor version: with 2 bugfix : https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.8.1

Unclear duplicated fields in config panel

Describe the bug

The installation process fails

Context

• Hardware: VPS bought online
• YunoHost version: 11.0.10.2
• I have access to my server: Through SSH
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no

Steps to reproduce

• open the config panel in the admin section
• see this:
  

Expected behavior

There should be three different descriptions for three different values, but the same description is repeated three times.

update to 0.9 failed

Currently in gts 0.8.1-ynh, installed on up to date YNH server in rasPi 4

two diferent issues? unrelated?

FULL LOG

2023-05-25 11:15:49,723: DEBUG - + out='Will not apply HSTS. The HSTS database must be a regular and non-world-writable file.
2023-05-25 11:15:49,724: DEBUG - ERROR: could not open HSTS store at '\''/root/.wget-hsts'\''. HSTS will be disabled.
2023-05-25 11:15:49,724: DEBUG - https://github.com/superseriousbusiness/gotosocial/releases/download/v0.9.0/gotosocial_0.9.0linux_arm64.tar.gz:
2023-05-25 11:15:49,725: DEBUG - 2023-05-25 11:15:49 ERROR 404: Not Found.'
2023-05-25 11:15:49,725: DEBUG - + ynh_die '--message=Will not apply HSTS. The HSTS database must be a regular and non-world-writable file.
2023-05-25 11:15:49,725: DEBUG - ERROR: could not open HSTS store at '\''/root/.wget-hsts'\''. HSTS will be disabled.
2023-05-25 11:15:49,725: DEBUG - https://github.com/superseriousbusiness/gotosocial/releases/download/v0.9.0/gotosocial_0.9.0linux_arm64.tar.gz:
2023-05-25 11:15:49,726: DEBUG - 2023-05-25 11:15:49 ERROR 404: Not Found.'
2023-05-25 11:15:49,728: DEBUG - ERROR: could not open HSTS store at '\''/root/.wget-hsts'\''. HSTS will be disabled.
2023-05-25 11:15:49,729: DEBUG - https://github.com/superseriousbusiness/gotosocial/releases/download/v0.9.0/gotosocial_0.9.0linux_arm64.tar.gz:
2023-05-25 11:15:49,729: DEBUG - 2023-05-25 11:15:49 ERROR 404: Not Found.'
2023-05-25 11:15:49,771: DEBUG - ERROR: could not open HSTS store at '\''/root/.wget-hsts'\''. HSTS will be disabled.
2023-05-25 11:15:49,772: DEBUG - https://github.com/superseriousbusiness/gotosocial/releases/download/v0.9.0/gotosocial_0.9.0linux_arm64.tar.gz:
2023-05-25 11:15:49,772: DEBUG - 2023-05-25 11:15:49 ERROR 404: Not Found.'
2023-05-25 11:15:49,773: DEBUG - + ynh_exit_properly
2023-05-25 11:15:49,783: WARNING - Will not apply HSTS. The HSTS database must be a regular and non-world-writable file.
2023-05-25 11:15:49,785: WARNING - ERROR: could not open HSTS store at '/root/.wget-hsts'. HSTS will be disabled.

and

2023-05-25 11:17:09,879: DEBUG - 51003 Wi-Fi is currently blocked by rfkill.
2023-05-25 11:17:09,882: DEBUG - 51006 Use raspi-config to set the country before use.
2023-05-25 11:17:09,883: DEBUG - 51007
2023-05-25 11:17:10,036: WARNING - 51159 ERROR:  syntax error at or near "Wi"
2023-05-25 11:17:10,038: WARNING - 51161 LINE 1: Wi-Fi is currently blocked by rfkill.
2023-05-25 11:17:10,040: WARNING - 51161 

later seems a problem with "-" in Wi-Fi when update script is run

thank you!

BIG logfile

TL;DR

gts log file is almost 1Gb in size, is this normal? Can it be mitigated manually setting more restrictive values in the config? does it need to be that big? Thank you.

I've not edited or changed default settings neither for gts nor yunohost

Issue

as I have very small VPS (debian 11, x64, ynh 11.2.5, gts 0.12.1) so I check space available from time to time and I noticed what I consider a very big logfile for gotosocial, and is also true compared to other services:

root@SERVER:~#du -h -d 1 /var/log/
4.0K    /var/log/chrony
361M    /var/log/journal              <-------------------- 361M 
4.0K    /var/log/sysstat
12K     /var/log/runit
76K     /var/log/apt
39M     /var/log/yunohost
4.0K    /var/log/ntpstats
12M     /var/log/nginx
6.9M    /var/log/postgresql
932M    /var/log/gotosocial__2           <----------------------   932M
4.0K    /var/log/private
364K    /var/log/gemserv
4.0K    /var/log/mysql
900K    /var/log/borg
164K    /var/log/rspamd
32K     /var/log/redis
44K     /var/log/unattended-upgrades
212K    /var/log/metronome
1.4G    /var/log/           <------------------   TOTAL SIZE

gotosocial__2 is about 2/3 of total size :/ That catched my eye.

Reading gotosocial's logrotate config:

root@SERVER:~#cat /etc/logrotate.d/gotosocial__2 
/var/log/gotosocial__2/*.log {
        # Rotate if the logfile exceeds 100Mo
    size 100M       <--------   **this setting DOES NOT apply  (932 > 100), but as there's only one file I guess it is not "rotated"**
        # Keep 12 old log maximum
    rotate 12
        # Compress the logs with gzip
    compress
        # Compress the log at the next cycle. So keep always 2 non compressed logs
    delaycompress
        # Copy and truncate the log to allow to continue write on it. Instead of move the log.
    copytruncate
        # Do not do an error if the log is missing
    missingok
        # Not rotate if the log is empty
    notifempty
        # Keep old logs in the same dir
    noolddir
    
}

root@SERVER:~#ls -la /var/log/gotosocial__2/
total 953444
drwxrwxrwx  2 root root      4096 Sep  3 05:27 .
drwxr-xr-x 20 root root      4096 Nov  1 00:00 ..
-rw-r--r--  1 root root 976312927 Nov  1 17:06 gotosocial__2.log        <------- **one single log file** 

in /var/www/gotosocial__2/config.yaml we have log-level: "info", would this log level cause such a big file?

So, any thoughts would be appreciated, thank you.

fetching issues

Describe the bug

i encountering fetching issues that dont seem to happen on gts server not installed thought ynh.
the issues are:

• random post fetching issues (error 500)
  

• inability to "steal" or upload custom emojis on my instance
  

• other instance (and also some clients like phanpy) cannot fetch the avatar of the accounts on my instance
  

Context

• Hardware: VPS bought online
• YunoHost version: 11.1.20
• I have access to my server: Through SSH | through the webadmin
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• Using, or trying to install package version/branch: 0.8.1~ynh1

Steps to reproduce

try to fetch toots and/or accounts from links (with some it works) and/or try to add custom emojis in any of the available ways.

Expected behavior

being able to fetch toots, accounts and add custom emoji.

Logs

the log is from a couple of weeks ago because it's when i reported it to gts and found out it must be a ynh issue.

Allow CSS setting is not kept on upgrade

Describe the bug

most instance settings are corretly set to previous values after upgrading, but "allow personal css" is not.

Context

gotosocial 0.8.0 (it happens since previous versions too) in latest stable YNH server (11.1.17, 64bit, etc.)

Steps to reproduce

• set "allow css" to true in yunohost gotosocial config panel.
• upgrade gotosocial

Expected behavior

true (or value set) should persist on upgrading as other values in config panel do

Thank you.

[question] is link to media broken?

it looks like so:

timestamp="26/05/2023 05:48:09.400" func=middleware.Logger.func1.1 level=INFO latency="338.203µs" userAgent="Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/113.0" method=GET statusCode=404 path=/fileserver/01VHYNX1AAVTTWR567M7NBM6SS/attachment/original/01BGMYST9724MNPRBPRTHDET54.png clientIP=195.xxx.yyy.200 requestID=q2t64cccccccccccc00awrs8rg msg="Not Found: wrote 21B"

it happens with all previouly published pictures

It does not load multimedia (pictures) posted by user in any recent post.

I've test publishing a new picture and it was published, but non of the previous pictures are shown.

01BGMYST9724MNPRBPRTHDET54.png is not in that directory

$ ls 01VHYNX1AAVTTWR567M7NBM6SS/attachment/original
01AZRBYWJ02GB6Q2Z3HZSCC41T.jpg  01PTB3DZJAVBWXEH3522PW49K5.jpg

Updated to 0.9 ynh-2 from 0.8.1