Обсуждение: wiki log in: "Resource available only to logged in users"
Based on visiting https://www.postgresql.org/account/profile/, this Chrome profile is logged into my community account. However, if I visit https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items and click "log in" or "view source" I get: Error 403 Resource available only to logged in users Resource available only to logged in users Guru Meditation: XID: 391363 I get the same in a Chrome incognito window. I've not seen this error before today, though I've likely not logged into the wiki since before the PostgreSQL 18.0 release.
On 12/5/25 12:24, Noah Misch wrote: > Based on visiting https://www.postgresql.org/account/profile/, this Chrome > profile is logged into my community account. However, if I visit Not following, how is a Chrome profile involved? AFAIK you log with an email. > https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items and click "log in" > or "view source" I get: > > Error 403 Resource available only to logged in users > Resource available only to logged in users > Guru Meditation: > XID: 391363 > > I get the same in a Chrome incognito window. I've not seen this error before > today, though I've likely not logged into the wiki since before the PostgreSQL > 18.0 release. > > -- Adrian Klaver adrian.klaver@aklaver.com
On Fri, Dec 05, 2025 at 12:47:04PM -0800, Adrian Klaver wrote: > On 12/5/25 12:24, Noah Misch wrote: > > Based on visiting https://www.postgresql.org/account/profile/, this Chrome > > profile is logged into my community account. However, if I visit > > Not following, how is a Chrome profile involved? I just meant "this browser is logged into my community account". I highlighted this to avoid responses like "did you try logging in?" (My original post said it in terms of Chrome profiles because each profile has its own store of cookies. Logging into postgresql.org in one profile wouldn't achieve that for any other profile. This detail probably doesn't matter for fixing $SUBJECT.) > AFAIK you log with an email. Correct. > > https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items and click "log in" > > or "view source" I get: > > > > Error 403 Resource available only to logged in users > > Resource available only to logged in users > > Guru Meditation: > > XID: 391363 > > > > I get the same in a Chrome incognito window. I've not seen this error before > > today, though I've likely not logged into the wiki since before the PostgreSQL > > 18.0 release.
On 12/5/25 13:05, Noah Misch wrote: > On Fri, Dec 05, 2025 at 12:47:04PM -0800, Adrian Klaver wrote: >> On 12/5/25 12:24, Noah Misch wrote: >>> Based on visiting https://www.postgresql.org/account/profile/, this Chrome >>> profile is logged into my community account. However, if I visit >> >> Not following, how is a Chrome profile involved? > > I just meant "this browser is logged into my community account". I > highlighted this to avoid responses like "did you try logging in?" (My > original post said it in terms of Chrome profiles because each profile has its > own store of cookies. Logging into postgresql.org in one profile wouldn't > achieve that for any other profile. This detail probably doesn't matter for > fixing $SUBJECT.) Alright I understand. I have had issues before with incomplete log outs/ins. If the Logout link is present under the Quick Links section on the left side of the page try logging out and then back in. > >> AFAIK you log with an email. > > Correct. > -- Adrian Klaver adrian.klaver@aklaver.com
On Fri, Dec 05, 2025 at 01:15:56PM -0800, Adrian Klaver wrote: > On 12/5/25 13:05, Noah Misch wrote: > > On Fri, Dec 05, 2025 at 12:47:04PM -0800, Adrian Klaver wrote: > > > On 12/5/25 12:24, Noah Misch wrote: > > > > Based on visiting https://www.postgresql.org/account/profile/, this Chrome > > > > profile is logged into my community account. However, if I visit > > > > > > Not following, how is a Chrome profile involved? > > > > I just meant "this browser is logged into my community account". I > > highlighted this to avoid responses like "did you try logging in?" (My > > original post said it in terms of Chrome profiles because each profile has its > > own store of cookies. Logging into postgresql.org in one profile wouldn't > > achieve that for any other profile. This detail probably doesn't matter for > > fixing $SUBJECT.) > > Alright I understand. I have had issues before with incomplete log outs/ins. > If the Logout link is present under the Quick Links section on the left side > of the page try logging out and then back in. That did not change the outcome. Does https://wiki.postgresql.org/index.php?title=PostgreSQL_18_Open_Items&action=edit work for you, or does it give the error I reported?
On 12/5/25 13:27, Noah Misch wrote: > On Fri, Dec 05, 2025 at 01:15:56PM -0800, Adrian Klaver wrote: >> On 12/5/25 13:05, Noah Misch wrote: >>> On Fri, Dec 05, 2025 at 12:47:04PM -0800, Adrian Klaver wrote: >>>> On 12/5/25 12:24, Noah Misch wrote: >>>>> Based on visiting https://www.postgresql.org/account/profile/, this Chrome >>>>> profile is logged into my community account. However, if I visit >>>> >>>> Not following, how is a Chrome profile involved? >>> >>> I just meant "this browser is logged into my community account". I >>> highlighted this to avoid responses like "did you try logging in?" (My >>> original post said it in terms of Chrome profiles because each profile has its >>> own store of cookies. Logging into postgresql.org in one profile wouldn't >>> achieve that for any other profile. This detail probably doesn't matter for >>> fixing $SUBJECT.) >> >> Alright I understand. I have had issues before with incomplete log outs/ins. >> If the Logout link is present under the Quick Links section on the left side >> of the page try logging out and then back in. > > That did not change the outcome. > > Does > https://wiki.postgresql.org/index.php?title=PostgreSQL_18_Open_Items&action=edit > work for you, or does it give the error I reported? I get the same error, also when I try to use the Search dialog. Seems there is something else in play here. -- Adrian Klaver adrian.klaver@aklaver.com
On 2025-Dec-05, Noah Misch wrote: > Based on visiting https://www.postgresql.org/account/profile/, this Chrome > profile is logged into my community account. However, if I visit > https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items and click "log in" > or "view source" I get: > > Error 403 Resource available only to logged in users Hello, The wiki had been "under attack" (read: unnaturally heavy scraping traffic) for a few days and had consequently started spewing errors of various kinds. To defend against this, some URLs had to be blocked, which is why you now get error 403 in various places. You should be able to log in to the wiki from its main page, and then all restrictions are lifted. It's not clear to me exactly why does the login link work on the main page and not on other pages. We may be able to lift this at some point. But for now, there's at least a workaround. Thanks, -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "I apologize for the confusion in my previous responses. There appears to be an error." (ChatGPT)
On 12/5/25 21:24, Noah Misch wrote: > Based on visiting https://www.postgresql.org/account/profile/, this Chrome > profile is logged into my community account. However, if I visit > https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items and click "log in" > or "view source" I get: > > Error 403 Resource available only to logged in users > Resource available only to logged in users > Guru Meditation: > XID: 391363 > > I get the same in a Chrome incognito window. I've not seen this error before > today, though I've likely not logged into the wiki since before the PostgreSQL > 18.0 release. I made an attempt to improve this - please try again! Stefan
On 12/6/25 02:02, Stefan Kaltenbrunner wrote: > On 12/5/25 21:24, Noah Misch wrote: > I made an attempt to improve this - please try again! It worked for me. Thanks. > > > Stefan > > -- Adrian Klaver adrian.klaver@aklaver.com
On Sat, Dec 06, 2025 at 09:28:35AM +0100, Álvaro Herrera wrote: > On 2025-Dec-05, Noah Misch wrote: > > Based on visiting https://www.postgresql.org/account/profile/, this Chrome > > profile is logged into my community account. However, if I visit > > https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items and click "log in" > > or "view source" I get: > > > > Error 403 Resource available only to logged in users > > Hello, > > The wiki had been "under attack" (read: unnaturally heavy scraping > traffic) for a few days and had consequently started spewing errors of > various kinds. To defend against this, some URLs had to be blocked, > which is why you now get error 403 in various places. You should be > able to log in to the wiki from its main page, and then all restrictions > are lifted. > > It's not clear to me exactly why does the login link work on the main > page and not on other pages. We may be able to lift this at some point. > But for now, there's at least a workaround. On Sat, Dec 06, 2025 at 11:02:51AM +0100, Stefan Kaltenbrunner wrote: > I made an attempt to improve this - please try again! I get the same error outcome from the main-page login link, which for me is https://wiki.postgresql.org/index.php?title=Special:UserLogin&returnto=Main+Page Visiting https://wiki.postgresql.org/wiki/Special:UserLogin is an effective workaround for me.
On 12/6/25 21:12, Noah Misch wrote: > On Sat, Dec 06, 2025 at 09:28:35AM +0100, Álvaro Herrera wrote: >> On 2025-Dec-05, Noah Misch wrote: >>> Based on visiting https://www.postgresql.org/account/profile/, this Chrome >>> profile is logged into my community account. However, if I visit >>> https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items and click "log in" >>> or "view source" I get: >>> >>> Error 403 Resource available only to logged in users >> >> Hello, >> >> The wiki had been "under attack" (read: unnaturally heavy scraping >> traffic) for a few days and had consequently started spewing errors of >> various kinds. To defend against this, some URLs had to be blocked, >> which is why you now get error 403 in various places. You should be >> able to log in to the wiki from its main page, and then all restrictions >> are lifted. >> >> It's not clear to me exactly why does the login link work on the main >> page and not on other pages. We may be able to lift this at some point. >> But for now, there's at least a workaround. > > On Sat, Dec 06, 2025 at 11:02:51AM +0100, Stefan Kaltenbrunner wrote: >> I made an attempt to improve this - please try again! > > I get the same error outcome from the main-page login link, which for me is > https://wiki.postgresql.org/index.php?title=Special:UserLogin&returnto=Main+Page > > Visiting https://wiki.postgresql.org/wiki/Special:UserLogin is an effective > workaround for me. yeah I think this was me simply not deploying all of the config changes - sorry for that.... Should work now... Stefan >
On Sat, Dec 06, 2025 at 09:36:16PM +0100, Stefan Kaltenbrunner wrote: > On 12/6/25 21:12, Noah Misch wrote: > > On Sat, Dec 06, 2025 at 11:02:51AM +0100, Stefan Kaltenbrunner wrote: > > > I made an attempt to improve this - please try again! > > > > I get the same error outcome from the main-page login link, which for me is > > https://wiki.postgresql.org/index.php?title=Special:UserLogin&returnto=Main+Page > > > > Visiting https://wiki.postgresql.org/wiki/Special:UserLogin is an effective > > workaround for me. > > yeah I think this was me simply not deploying all of the config changes - > sorry for that.... > > Should work now... Works now. Thanks.