SETtoolkit fails when attempting to clone URL with a SSL config

[benjimoralesperez]

Issue: SSL Configuration in SEToolkit Fails with Socket Error or PEM Passphrase Prompt

I'm running SEToolkit in my own environment and attempting to serve a cloned site over HTTPS. Here's the situation:

I have WEBATTACK_SSL=ON in set.config, as expected.

I’ve tried both SELF_SIGNED_CERT=ON and SELF_SIGNED_CERT=OFF.

When SELF_SIGNED_CERT=ON, SEToolkit generates its own certificate — but it prompts for a PEM passphrase at runtime, which I cannot bypass.

I don’t mind using the default certs if they worked without prompting, but they always require a passphrase.

To avoid this, I generated my own certificate and key using OpenSSL with the -nodes flag (so no passphrase is required).

I set SELF_SIGNED_CERT=OFF and pointed CERT_PATH and KEY_PATH to my own files.

However, when I run SEToolkit with this setup, it fails with a "socket server not defined" error and does not launch the HTTPS server.

Everything works fine when using the default HTTP config, but switching to SSL — either with SEToolkit’s own certs or my own — results in either a passphrase prompt or a socket error.

Would appreciate any guidance on how to properly configure SSL without triggering the passphrase prompt or socket failure.