Hi Guys,

Testing a MagiChat server, it's running on one of my VPS's so it's got a
fast connection and in a datacentre.

Please test and report back.

Address: ftn.vk3heg.net
Port: 18920





\/orlon
VK3HEG


--- MagickaBBS v0.15alpha (Linux/armv6l)
* Origin: \/orlon Empire: Sector 550 (21:1/195.1)

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?



|08---
|15++ |13Alpha |15++
|03TheDrunkenGamer.com|08:|078888
|08A Talisman BBS


--- Talisman v0.16-dev (Linux/x86_64)
* Origin: The Drunken Gamer BBS (21:4/158.1)

On 30 Mar 2021, Alpha said the following...

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 was able to connect locally, also got the cert error.

I can't make it run as a door in Mystic.

(D3) Exec DOOR32 Program
Data: MagiChatDoor.exe -D %Pdoor32.sys

Am I missing something?

|01 ├|06HSM|01─|14aka|01─|07Ga|08ry|01───────────────┐
|14 ┐|01│ Mystic|14.|01BBSGameTime|14.|01com|14:|0323|01 │|14┌
│|01│ ScoobysDoo|14.|01ddns|14.|01net|14:|032023|01 │|14│
│|01└───────────────────────────┘|14│

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: BBS GameTime - mystic.BBSGameTime.com:23 (21:2/162)

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.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!


--- Talisman v0.16-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

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.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!


--- Talisman v0.16-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

Hi Alpha,

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?

I get the same thing. My cert is a letencrypt cert created just for this testing. It was a run and see exercise just to get it going.




\/orlon
VK3HEG


--- MagickaBBS v0.15alpha (Linux/armv6l)
* Origin: \/orlon Empire: Sector 550 (21:1/195.1)

Hi Apam,

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.

/v gives me:

Cert Subject: /CN=ftn.vk3heg.net
Cert Issuer: /C=US/O=Let's Encrypt/CN=R3
Cert Status: unable to get local issuer certificate


Btw: I searched last nignt but came up empty. So will ask here.

Will MagicChatDoor work with Magicka and how do I configure the bbs?




\/orlon
VK3HEG


--- MagickaBBS v0.15alpha (Linux/armv6l)
* Origin: \/orlon Empire: Sector 550 (21:1/195.1)

On 31 Mar 2021, apam said the following...

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.

Thanks, one .bat later and it works fine!

|01 ├|06HSM|01─|14aka|01─|07Ga|08ry|01───────────────┐
|14 ┐|01│ Mystic|14.|01BBSGameTime|14.|01com|14:|0323|01 │|14┌
│|01│ ScoobysDoo|14.|01ddns|14.|01net|14:|032023|01 │|14│
│|01└───────────────────────────┘|14│

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: BBS GameTime - mystic.BBSGameTime.com:23 (21:2/162)

Not sure what's going on there. Looks like it needs to be updated

OK, working now!

Server = thedrunkengamer.com
Port = 18920



|08---
|15++ |13Alpha |15++
|03TheDrunkenGamer.com|08:|078888
|08A Talisman BBS


--- Talisman v0.16-dev (Linux/x86_64)
* Origin: The Drunken Gamer BBS (21:4/158.1)

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?

The door will work with Magicka, the built in magichat doesn't have SSL support, so you will need to use the door.

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.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!


--- Talisman v0.16-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

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.

I have the folling files in the magichat server dir:

cert.pem
chain.pem
fullchain.pem
key.pem

other wise the magichat server complains and wont start...

Could you add the feature of being able to link server's, so that there's
not just a heap of standalone servers?

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.

As you've taken down the Magicka documentation, I have nothing to
referance! Will give it a try tomorrow.





\/orlon
VK3HEG


--- MagickaBBS v0.15alpha (Linux/armv6l)
* Origin: \/orlon Empire: Sector 550 (21:1/195.1)

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)!




|08---
|15++ |13Alpha |15++
|03TheDrunkenGamer.com|08:|078888
|08A Talisman BBS


--- Talisman v0.16-dev (Linux/x86_64)
* Origin: The Drunken Gamer BBS (21:4/158.1)

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

Andrew
--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!


--- Talisman v0.16-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

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

I'll configure this at some point. ;) I disabled it on the BBS when
apam took his down, but won't take long to throw it back online.

Shawn

... Honk if you love peace and quiet!

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

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)!

Seems I don't need to setup a server, I was going to set mine up on a VPS as well, and I already have the SSL certs.


... This message uses 100% recycled electrons
=== MultiMail/Win v0.52
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

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)!

Connected!

|01 ├|06HSM|01─|14aka|01─|07Ga|08ry|01───────────────┐
|14 ┐|01│ Mystic|14.|01BBSGameTime|14.|01com|14:|0323|01 │|14┌
│|01│ ScoobysDoo|14.|01ddns|14.|01net|14:|032023|01 │|14│
│|01└───────────────────────────┘|14│

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: BBS GameTime - mystic.BBSGameTime.com:23 (21:2/162)

Hi apam,

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.

That's what I had to do to get it going, and there are nolonger any cert errors.

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

Thanks. I now have the door working from the bbs, but it's a bit dead
with no one else connected. #-(

\/orlon



\/orlon
VK3HEG


--- MagickaBBS v0.15alpha (Linux/armv6l)
* Origin: \/orlon Empire: Sector 550 (21:1/195.1)

Hi Alpha,

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. #-)

\/orlon



\/orlon
VK3HEG


--- MagickaBBS v0.15alpha (Linux/armv6l)
* Origin: \/orlon Empire: Sector 550 (21:1/195.1)

On 06 Apr 2021 at 12:32p, vorlon pondered and said...

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. #-)

I'd like to spin one up as well. Spent last night playing with the
client/door again and can recall the feedback I was passing to Andrew at the time.

Sorting the cert for the magichat server I'd like to look at running for fsxnet.nz is something I'm not so sure how to tackle as my webhost has one already for the website etc. I'm not sure if I can raise something specific
for a subdomain and have that sat on my own computer or not.

The joys of learning by doing.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Could you add the feature of being able to link server's, so
that there's not just a heap of standalone servers?

I'm not the author of the software, that'd be Apam. But...

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 :)

-+-+-
Alpha
-+-+-
--- SBBSecho 3.13-Linux
* Origin: ALPHACOMPLEX.US (21:4/158)

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!

Yeah, I don't really want to add relaying, if all it gets is a bunch of
unused servers talking to each other.

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 :)

Yeah, someone needs to be motivated to actually turn up each week even if
it means idling by themselves for an hour or so - because if people do
turn up and no one is there, they will leave. I noticed on my server when
I was running it, plenty of people connected, just not at the same time.

I'm not all that motivated to be honest. I'm happy to chat etc, but given timezones, it can be a pain to get there every week at a time that suits
most.

I don't really see this happening, I'd love to be wrong, but I think most
who have a BBS will pick one or the other and 99% of the time they will
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.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!


--- Talisman v0.16-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

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.

This reminds me that I was looking at my main menu, and thinking about how I could probably get rid of a couple more of the features, or at least hide
them.

But making something better by subtraction is not an easy concept, a lot of
the time.

(Also, I only run FSXnet and Fidonet, at this point. That seems like enough. And I'd probably cut Fidonet if it weren't for the nostalgia aspects of a network that's stuck in the 80s.)

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Storm BBS (21:2/108)