Replying to Avatar G.M.Joe

Hey nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpz4mhxue69uhkvun9deejuat50phjummwv5hsz8rhwden5te0wfjkccte9e3xjarrda5kuurpwf4jucm0d5hsz9thwden5te0wfjkccte9e6hg7r09ehkuef0avzrjf

I set up aegis server here: aegis.relayted.de.

It is working fine via Websocket Secure in amethyst. I already paid the subscription twice and it still tells me that I don't have a subscription when trimming to upload media via blossom server.

When viewing the database in sqlite3 it shows me my npub. But not date of payment, expiry, and a "0" in "active subscription" field.

Can you please help? Of course after Christmas days! Happy christmas to you and your family.

Thanks for the great software you write!

You need an SSL certificate on your server, the webhook keeps failing, you should be able to see the error in webhook deliveries

Reply to this note

Please Login to reply.

Discussion

thanks for the answer. of course I have a certificate and I can reach the server via https and wss.

every single page on that server is working just fine. see screenshot.

browsershots just works fine too.

I can't see any webhook deliveries in bitvora backend.

My backend doesn't trust your certificate issuer. I'll look into this after Christmas maybe I'll just allow any ssl cert

next time fiatjaf asks why we arent done yet: ssl fr

Oh. Okay. It's a certificate bought via ionos. Take your time and have it nice!

Thanks again for assistance!

Try what? Uploading or paying the subscription? Because I manually edited the db so I can test functionality I have to take it back to see if it works after payment. Will do so later when at home.

Thanks for remembering me!

🙏

Yes just try to subscribe to your own relay, I made it so the webhook should trust any ssl certificates (I hope)

Paid it. Balance visible on bitvora.

I can't see any confirmation on the website. I can see that lock.mdb was changed upon payment. But subscriptions.db was not changed.

I see the webhook isn't failing anymore. I think something is out of sync since you manually updated the db. Maybe test it out with my npub and see if it all works smoothly now. Maybe quickly change your fee to be lower to minimize your bitvora fees to test

Will look into this tomorrow morning.

Hi there!

So i tried again. First is a payment for my npub. Second one for yours. I can see your hex and npub in subsription.db. but other fields are empty.

The third payment of 100 Sats is made with a "vanilla" index.php and a blank subsrciptions.db. I still can see the npub and hex, but active and both timestamp fields are empty.

Can you dump the journalctl -u aegis here pls

Just restarted it. But there is nothing else then this. Before stopping there was only the hourly "Checked and updated expired subscriptions". No log about new subscription, payment whatsoever.

aegis[192340]:

aegis[192340]: █████╗ ███████╗ ██████╗ ██╗███████╗

aegis[192340]: ██╔══██╗██╔════╝██╔════╝ ██║██╔════╝

aegis[192340]: ███████║█████╗ ██║ ███╗██║███████╗

aegis[192340]: ██╔══██║██╔══╝ ██║ ██║██║╚════██║

aegis[192340]: ██║ ██║███████╗╚██████╔╝██║███████║

aegis[192340]: ╚═╝ ╚═╝╚══════╝ ╚═════╝ ╚═╝╚══════╝

aegis[192340]: PREMIUM RELAY & BLOSSOM SERVER

aegis[192340]:

aegis[192340]: 2024/12/28 09:49:06 🚀 Aegis is booting up

aegis[192340]: 2024/12/28 09:49:06 🚀 Server started on port 8080

Maybe i should just start all over with a fresh aegis?

Yes I think this is a good idea

Still the same result. The page does not return a success message. I can see the hex and npub in db., however active contains 0, and both timestamp fields are empty.

If if you not getting logs then either:

- you haven't setup the webhook secret properly

- you haven't set the event to lightning deposit completed on bitvora

It should always log

log.Println("Received deposit.lightning.completed event", webhookPayload.Data.ID)

🤦‍♂️ Shame on me. I did not set the subdomain in the webhook. Now the page returns a success message!

In Germany we call it error 50: The error sits 50 cm in front of the screen!

Maybe i should start with a fresh db folder. I will look into this later.

Till now I never had issues with the certificates by ionos.