and welcome to the forums.
Generally, I would advise against using the 'any' interface, in both the SSLVPN setup and the policy. Probably you plan to use the SSLVPN from an external network so the obvious port would be 'wan1'.
If you enable the same SSLVPN portal on both the 'wan1' and 'lan' ports, how is that supposed to work if the client's IP is assigned from the same IP pool? One interface, one portal, one IP pool, and routing will work.(This is not the root cause of the connection timeout but you'll run into this later.)
Then, just to exclude a port error, move the SSLVPN port to, for instance, 10443 and try to connect to "myWANIP:10443". If that does work you've got port 443 used somewhere else.
"Kernel panic: Aiee, killing interrupt handler!"