Can't register SFV4C6 to Central nor via OTP neither via account

Hello TomasLavicky,

Thank you for reaching out to the community, can you share the following logs here:
> Log file details: https://docs.sophos.com/nsg/sophos-firewall/19.0/Help/en-us/webhelp/onlinehelp/AdministratorHelp/Logs/LogFileDetails/index.html
1.)  tail -f /log/centralmanagement.log

Hello Vivek,

here are:

SF01V_VM01_SFOS 19.0.1 MR-1-Build365# tail -f /log/centralmanagement.log
2022-08-23 07:06:22Z FATAL central-connect[22396]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 07:06:50Z FATAL central-connect[22492]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 07:07:37Z FATAL central-connect[22702]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 07:33:25Z FATAL central-connect[26830]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 08:18:47Z FATAL central-connect[32345]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 08:34:59Z FATAL central-connect[1515]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 08:35:54Z FATAL central-connect[1635]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 08:39:49Z FATAL central-connect[2017]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 08:54:14Z FATAL central-connect[4588]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.
2022-08-23 08:56:00Z FATAL central-connect[4767]:59 main:: - Seems that we got called by accident since we are not registered. Exiting.

SF01V_VM01_SFOS 19.0.1 MR-1-Build365# tail -f /log/sophos-central.log  
2022-08-23 08:56:01Z WARN API.pm[4771]:119 SFOS::Common::Central::API::send_request - 400 URL must b
e absolute
Content-Type: text/plain
Client-Date: Tue, 23 Aug 2022 08:56:01 GMT
Client-Warning: Internal response

400 URL must be absolute
 
2022-08-23 08:56:01Z INFO central-register[4771]:287 main::_unregister - Removing JSON configuration
file  
2022-08-23 08:56:01Z INFO central-register[4771]:293 main::_unregister - Removing central customer i
nfo JSON file  
2022-08-23 08:56:02Z INFO central-register[4776]:129 main::_create_storage_and_init_json_config - Cr
eate sophos-central-customer-info.json file

I unregistered old instance in Sophos Central first and in Sophos Firewall itself then. Could it be the problem?

It may or may not be:
================
Can you try the following steps from the advance shell:
================
Step1: central-register --status
Step2: central-register --unregister
=================
And then try again the registration process - along side run the tail -f /log/centralmanagement.log logs as too...

It may or may not be:
================
Can you try the following steps from the advance shell:
================
Step1: central-register --status
Step2: central-register --unregister
=================
And then try again the registration process - along side run the tail -f /log/centralmanagement.log logs as too...

SF01V_VM01_SFOS 19.0.1 MR-1-Build365# central-register --status
This SFOS instance is currently not registered with Sophos Central
SF01V_VM01_SFOS 19.0.1 MR-1-Build365# central-register --unregister
Use of uninitialized value in concatenation (.) or string at /usr/bin/central-register line 279.
Use of uninitialized value in concatenation (.) or string at /usr/bin/central-register line 279.
Use of uninitialized value in concatenation (.) or string at /usr/bin/central-register line 280.
{"result":"SUCCESS","cloud_company_name":"","cloud_token":"","cloud_hb_availability":0}

Still the same logs in /log/centralmanagement.log.

Can you share the cat output I want to check which central url it hits !! 
Cat /log/centralmanagement.log.

It's already settled. I didn't realize that I didn't transfer the license when I installed VI-18.5.4_MR-4.VMW-418.zip because of the VI-19.0.1_MR-1.VMW-365.sig upgrade first. It works now. Thanks for the help.

awesome, cheers !! TomasLavicky