Please test and report back.
Address: ftn.vk3heg.net
Port: 18920
Please test and report back.
Address: ftn.vk3heg.net
Port: 18920
Hey vorlorn! I connected finr, but I get this error message at the top of the screen in MagiChat:
There was an SSL error connecting, see /cert for details
I can't make it run as a door in Mystic.
ones that my web sewrver are using. Still got the error.
Wonder if Apam has any advice?
Please test and report back.
Address: ftn.vk3heg.net
Port: 18920
Hey vorlorn! I connected finr, but I get this error message at the
top of the screen in MagiChat:
|04There was an SSL error connecting, see /cert for details
|08Note, i got the same error when I tried setting up my own
server. I tried using both new;y created certs/pem files, and also
copied over the ones that my web sewrver are using. Still got the
error.
Wonder if Apam has any advice?
ones that my web sewrver are using. Still got the error.
Wonder if Apam has any advice?
Not sure what's going on there. Looks like it needs to be updated
/v gives version and certificate info not /cert
also those help files are way out dated. I'll see if I can find the
latest ones and update the git repo.
I can't make it run as a door in Mystic.
Make sure you run it from the directory with the ini file in it.
you may need to make a batch file to change directory first.
Not sure what's going on there. Looks like it needs to be updated
Cert Status: unable to get local issuer certificate
Will MagicChatDoor work with Magicka and how do I configure the bbs?
Cert Status: unable to get local issuer certificate
Are you using the fullchain.pem or cert.pem?
I think from memory I had to use fullchain.pem as the cert.
Will MagicChatDoor work with Magicka and how do I configure the
bbs?
It's just the same as any other door in Magicka, make a shell
script and have it change to the magichat directory and then run
with:
./MagichatDoor -D /path/to/door.sys
You will need to modify the ini file as well. Oh and set it to use
STDIO mode.
Could you add the feature of being able to link server's, so that
there's
not just a heap of standalone servers?
I have the folling files in the magichat server dir:
cert.pem
chain.pem
fullchain.pem
key.pem
As you've taken down the Magicka documentation, I have nothing to
referance! Will give it a try tomorrow.
Alpha wrote to vorlon <=-
I've got mine working w/SSL (letsencrypt), but happy to defer to
someone else's server as well. It's on digital a digital ocean VPS:
Server = thedrunkengamer.com
Port = 18920
On 03-30-21 21:05, Alpha wrote to vorlon <=-
Could you add the feature of being able to link server's, so that
there's
not just a heap of standalone servers?
I've got mine working w/SSL (letsencrypt), but happy to defer to
someone else's server as well. It's on digital a digital ocean VPS:
Server = thedrunkengamer.com
Port = 18920
Feel free to connect (anyone)!
I've got mine working w/SSL (letsencrypt), but happy to defer to someone else's server as well. It's on digital a digital ocean VPS:
Server = thedrunkengamer.com
Port = 18920
Feel free to connect (anyone)!
I have the folling files in the magichat server dir:
cert.pem
chain.pem
fullchain.pem
key.pem
You might need to rename the fullchain.pem to cert.pem you can
remove chain.pem. It only uses cert.pem and key.pem. I think the fullchain.pem is cert.pem and chain.pem combined.
As you've taken down the Magicka documentation, I have nothing
to referance! Will give it a try tomorrow.
The documentation is here:
https://gitlab.com/magickabbs/magickabbs-documentation
Could you add the feature of being able to link server's, so
that there's not just a heap of standalone servers?
I've got mine working w/SSL (letsencrypt), but happy to defer to
someone else's server as well. It's on digital a digital ocean VPS:
See my previous message to apam. Mines now working, but it's pretty dead with only myself connecting.... Linking mutiple servsers together would make it better. Mines located in Australia. #-)
Could you add the feature of being able to link server's, so
that there's not just a heap of standalone servers?
I think all that's needed is a single, reliable server instance we can
all connect to, and it doesn't have to be mine!
I think more importantly, who is going to advocate for/advertise
usage? Get people to join at a certain time. That takes some elbow
grease :)
pick MRC, because it's established. This strangely opposite to echo nets, where everyone wants ALL the nets no matter how dead they are lol.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 54:19:30 |
Calls: | 8,066 |
Calls today: | 1 |
Files: | 13,055 |
Messages: | 5,841,551 |