Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
DarrelT
Explorer

Gaia Portal Recognized a non-valid username

Hi,

 

We install JHF take 84 on R81.20.

installation/update was successful, and we check services, and all are working normal. 

However, when we try to create a new snapshot on Gaia after the JHF Take 84 installation we get an error message "Gaia Portal recognized a non-valid username". 

we tried creating backup and it works. We create the snapshot on CLI and it works, it even shows the progress on Gaia. 

Can anyone tell me what's happening? 

(1)
10 Replies
PhoneBoy
Admin
Admin

Sounds like a bug, which should be reported via TAC: https://help.checkpoint.com 

0 Kudos
EY
Contributor

Hi @DarrelT, I've got the same problem here, but still on Take 54.  We'll be reporting to TAC unless you found a fix/workaround.

0 Kudos
torstenb
Explorer

Hello,

like @DarrelT said, it's possible to create a snapshot via Clish. After you have done the snapshot one time via Clish you are able, to create snapshots via GUI without the error "Gaia Portal recognized a non-valid username" again. Tests were made for R81.20 JHF 84.

 
 

 

 

the_rock
Legend
Legend

I never tried it in that jumbo, but just tested jumbo 90 and worked fine from web UI.

Andy

0 Kudos
Peter-Kyn
Participant

Hi,

I'm on R81.20 Jumbo Hotfix Take 98 and I got the same message ("Gaia Portal recognized a non-valid username"), when I tried to create a snapshot via GUI, in clish it is working fine...

Peter

_Val_
Admin
Admin

Did you open a TAC case yet?

Peter-Kyn
Participant

Not yet, as I got my Snapshot via clash...

0 Kudos
the_rock
Legend
Legend

I can test it in the lab shortly...give me an example of the username you tried this with?

Andy

0 Kudos
Peter-Kyn
Participant

In WebUI are only the default user created: admin and monitor...

I'm using an AD based user which is authenticated via RADIUS (looks like "abcd123")

Peter 

0 Kudos
DarrelT
Explorer

Hi Guyz,

I do apologize for late response here. We were able to fix the issue. 

We tried creating the snapshot and backup on CLI and it works. We also re install policy and the error was fix. 

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events