ukadon.shillest.net は、数々の独立したMastodonサーバーのうちのひとつです。サーバーに登録してFediverseのコミュニティに加わってみませんか。
うかどんはデスクトップマスコットソフト「伺か」向け主体(専用とは言ってない)のMastodonサーバです。うどんでも新手のどんぶりでもありません。

サーバーの情報

150
人のアクティブユーザー

@kanade_lab Could you please check the update file configuration of this ghost sometime?
I think maybe there is something wrong with it

@steve02081504 対応してみましたがどうでしょうか

@kanade_lab I'm still unable to update and it looks like I have a network problem (and it doesn't look like the ssp update cache is working either)
Maybe after pona fixes the update caching issue with ssp I'll get it done a few more times
Anyway, thanks for the help!

@steve02081504 アップデートのログにエラーが出てたりしますか?
先程はゴーストのフルアップロードを試しましたが、エラーの原因がわからないまま対応したので詳しく見ておきたいです。

・Ctrl+L
・Left-Bottom Combobox: Update

@kanade_lab This looks like the server is denying access on the way to download, although I'm not sure

@steve02081504
"server is denying access" の可能性… とりあえずブラウザで開いてみますか? ブラウザで開けるならSSPが怪しいのかもしれない
レンタルサーバーの問題でないと良いのですが

nanachi.sakura.ne.jp/twin/deve

@kanade_lab Even though I got an error updating ghost in ssp, I can still access the file normally in the browser
It does seem to be a ssp's issue.

@ponapalt Could you please check the relevant codes?
Thanks for your efforts :blobok:

@steve02081504 Please check network log. (not update log)

@steve02081504 There is a log that succeeds with HTTP code 304, so it is not an update cache issue.
Since it is stopping with a 502 error, it is probably an error on the server side or some cache server leading up to it.

@ponapalt I'm not quite sure about all this, does this mean nanachi needs to change the server used for ghost updates? :meow_thinking:

@steve02081504 A 502 Bad Gateway error is returned because an error occurred at one of the relay servers leading up to the nanachi.sakura.ne.jp server.
It may be a problem in your environment, or it may be a technical problem on the Sakura Internet side. At least on the SSP side, the only thing I can do is to increase the number of retries.

ぽな (C.Ponapalt)

@steve02081504 Does it happen even if you rewrite the homeurl from http to https?

@ponapalt Looks much better with https, but still ng (after about 50 files successfully updated)