The PATH for the [attachment] section is set to data/attachments in our config, I am going to check if using an absolute path (/var/lib/gitea/data/attachments) solved the issue. If so I'll create a PR with the fix
The `PATH` for the `[attachment]` section is set to `data/attachments` in our config, I am going to check if using an absolute path (`/var/lib/gitea/data/attachments`) solved the issue. If so I'll create a PR with the fix
greg
self-assigned this 2020-07-07 15:53:22 +00:00
I just checked again, since we upgraded Gitea in the meantime. I can upload in private repos as well now, but all attached images (including yours in this thread) are now just rendered as text links. :/
I just checked again, since we upgraded Gitea in the meantime. I can upload in private repos as well now, but all attached images (including yours in this thread) are now just rendered as text links. :/
I am going to check if using an absolute path (/var/lib/gitea/data/attachments) solved the issue. If so I’ll create a PR with the fix
Actually, the path needs to be changed to /mnt/data/gitea/... anyway. See #178
> I am going to check if using an absolute path (/var/lib/gitea/data/attachments) solved the issue. If so I’ll create a PR with the fix
Actually, the path needs to be changed to `/mnt/data/gitea/...` anyway. See #178
Update: it seems to happen for files past a certain size limit. But instead of complaining about the file being too large (which is a bit silly at 2MB e.g.), it just does nothing.
Update: it seems to happen for files past a certain size limit. But instead of complaining about the file being too large (which is a bit silly at 2MB e.g.), it just does nothing.
greg
was unassigned by raucao2020-08-05 13:51:03 +00:00
raucao
self-assigned this 2020-08-05 13:51:06 +00:00
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.
I can't upload anything in Gitea comments (and I think I hadn't tried since the migration).
There's no error message on the client side at all.
The
PATHfor the[attachment]section is set todata/attachmentsin our config, I am going to check if using an absolute path (/var/lib/gitea/data/attachments) solved the issue. If so I'll create a PR with the fixI just checked and I can't reproduce it, see the attached images to this comment
Could you try in a private repo perhaps? That's where it happened to me. (I wasn't able to upload in the end.)
I just checked again, since we upgraded Gitea in the meantime. I can upload in private repos as well now, but all attached images (including yours in this thread) are now just rendered as text links. :/
Actually, the path needs to be changed to
/mnt/data/gitea/...anyway. See #178Update: it seems to happen for files past a certain size limit. But instead of complaining about the file being too large (which is a bit silly at 2MB e.g.), it just does nothing.
For some reason it was just using nginx defaults, which is always extremely low for upload size. Changed it in production, PR incoming.