Please disregard the question above.

I did not realize the parm wallet_filename must equal just wallet name and not the whole path.

No:  wallet_filename = C:\Users\Martin\AppData\Roaming\Bitcoin\wallets\ElectrumPersonalServer\
Yes: wallet_filename = ElectrumPersonalServer

I wanted to rename the wallet electrumpersonalserver to ElectrumPersonalServer (add nicer camel-case).

According to what I found, it was to be enough to rename the folder in \AppData\Roaming\Bitcoin\wallets, which I did. Then I restarted the Bitcoin Core and indeed the wallet is available there under the new name.

However, when I started the EPS, I got:

Note the wallet *does* exist and *is* loaded. It seems that EPS does not recognize the renamed wallet for some reason.

I tried to delete the wallet and create it again both in GUI and in CLI:

In both cases, the result is the same like before:

I tried tweaking some parameters ((un-)commenting) in C:\Users\Martin\Documents\electrum-personal-server-windows-release-v0.2.4\config.ini:

None of this did the trick.

It can be even better like this if one wants to learn new things and take one's brain to the gym . But it's not for everybody. Moreover, without your hints, I do not think I would get it working on my own.

Also, it may be a good idea to generate a new cert from the security point of view. As the README.md says:
If your wallet connects over the public internet you should generate your own SSL certificate instead of using the default one, otherwise your connection can be decrypted.

I updated some related posts on reddit, so it may help someone too.

I checked the installation-supplied cert.crt and indeed it expired on Mar 12 00:07:58 2023 GMT.

I generated a new self-signed cert using OpenSSL with extended validity.

I started again both EPS and E. wallet ("C:\Program Files (x86)\Electrum\electrum-4.4.6.exe" --oneserver --server 127.0.0.1:50002:s).

And it worked!!  

But idiot as I'm, I had to fiddle with the cert - I wanted a really long validity to be future-proof. So I generated a new cert, exactly like before:

openssl genrsa -des3 -passout pass:x -out server.pass.key 2048
openssl rsa -passin pass:x -in server.pass.key -out cert.key
del server.pass.key
openssl req -new -key cert.key -out cert.csr
openssl x509 -req -days 4825 -in cert.csr -signkey cert.key -out cert.crt

But then the EPS <-> Wallet connection *stopped* working. The wallet refused to connect to EPS even though it was running fine - "Listening for Electrum Wallet on ('127.0.0.1', 50002)".

After a lot of swearing, I found out that Electrum Wallet keeps a suspiciously named file 127.0.0.1 in %AppData%\Roaming\Electrum\certs. The expectation was that it is the *old* cached cert that has already been overwritten in EPS. And because of cert-pinning, the fingerprint no longer matches.
And indeed, after I deleted the file 127.0.0.1 and restarted the Wallet, the connection works again (fingers crossed):


I think it's rather stupid to distribute software (EPS) with expired certificate without which it does not work. Also I do not quite get why SSL is needed in the first place since the components by default communicate via localhost on the same machine.

Anyway, thank you very much for help! BTC

What I want to achieve is to be able to query EPS on localhost instead of random Electrum server on the internet (which is the default option for the Electrum wallet).
If this works, I'd like to connect to EPS also from the Phoenix mobile wallet. I suppose port forwarding for port 50002 will be necessary to be set on the router. Plus some other auth stuff as the internet access is off by default, if I understood correctly.

As you suggested, I deleted the current wallet and created a new one without the descriptors.
It looks like things moved forward:

Now when I run "electrum-personal-server.exe config.ini", there are these extra lines in the output:

INFO:2023-09-27 19:44:00,823: Importing wallet 1/1
DEBUG:2023-09-27 19:44:01,606: Importing done
INFO:2023-09-27 19:44:01,606: Done.
If recovering a wallet which already has existing transactions, then
run the rescan script. If you're confident that the wallets are new
and empty then there's no need to rescan, just restart this script

After starting EPS again, it looks like EPS is available on 127.0.0.1:50002. This is also what the Electrum wallet is trying to connect to. Alas, the wallet does not seem to be able to connect:


Both EPS and wallet are running on the same machine.

- I followed the advice at https://github.com/chris-belcher/electrum-personal-server#how-to to set up a connection between Bitcoin Core v25 and Electrum Personal Server 0.2.4.
- I try to set it up on Windows 11 Pro.
- The Bitcoin Core is already installed, operational and fully synced - normally run with Ledger SatStack wallet. This works fine.

When issuing the suggested command , I get the following response:

I tried a variant without passphrase (if I got it right) too:
but I received exactly the same error message as before.

So I created the wallet manually in the GUI:


I then ran:

As I understand the correct message should be "Listening for Electrum Wallet ...", but it never appears. After I press "any key", the processing just ends.
Please note that the bc1 addresses above are correct and based on the master public key "electrumpersonalserver = zpub<omitted>" I have put in the config.ini file. This master pub key was extracted from Electrum wallet from Wallet -> Information.

I have checked the log file <omitted>AppData\Local\Temp\electrumpersonalserver.log, but there is nothing useful in there - just the same messages that appear in the PowerShell console above.

Any suggestion or help appreciated.