Re: Repos set back to read-write (was: Re: Replicated "The repository is temporarily read-only. Please try again later" (was: Re: Welcome Administrator Boone (was: Re: Problem with project link)))

On Fri, Dec 27, 2024 at 4:04 PM David Cooper <[email protected]>
wrote:

>
> Indeed all the repos had been set to read-only and were still stuck that
> way after restore.
>
> I've just reverted them to read_only: false, so please try again.
>
I can pull, but can't push.  And now I can't reach gitlab.c-l.net anymore;
I'm unable to connect again.


> Dave Cooper
>
>
>
> ---- On Fri, 27 Dec 2024 18:58:11 -0500 *David Cooper
> <[email protected] <[email protected]>>* wrote ---
>
>
> I am able to pull, but i'm replicating the "The repository is temporarily
> read-only. Please try again later."
>
> This may be a setting which was done on the old host before final backup
> and got carried into the new host through the restore. Looking into it...
>
> Dave Cooper
>
>
>
> ---- On Fri, 27 Dec 2024 18:55:07 -0500 *David Cooper
> <[email protected] <[email protected]>>* wrote ---
>
>
> Just noticed that the port 22 rule went missing from the nftables
> inputRules chain.
>
> I guess whatever I did failed to make it persistent.
>
> Just edited /etc/nftables.conf and rebooted, let's see what happens.  Port
> 22 being blocked certainly would explain inablity to push/pull...
>
> Dave Cooper
>
>
>
>
>
>
>
>
>
>

-- 
Ray