Ah interesting. Thanks for flagging! I should have fixed this in version 1.1.1. I added additional logic to check if “https://” is already present and if so to not append “https:”. Hope this fixes your issue