Online Home Poker (4 Viewers)

I've got some posts in this thread about how to expose Poker Mavens to the world using AWS:
https://www.pokerchipforum.com/threads/online-home-poker.54141/post-1052724
https://www.pokerchipforum.com/threads/online-home-poker.54141/post-1053149
https://www.pokerchipforum.com/threads/online-home-poker.54141/post-1057466

This gets a bit more complicated when you start to use https and your own domains (which I have some examples for here too). But since I figured you were starting small, the above links should help you out.
You are a great help !! i did every step you posted, got a little nervous bc I lost my connection to the VM and couldn't get logged in but managed to figure it out! Whats next ?? lmao

You are a great help !! i did every step you posted, got a little nervous bc I lost my connection to the VM and couldn't get logged in but managed to figure it out! Whats next ?? lmao
There is absolutely no way I would be able to do this without pic and step by step instructions..Thank you so much !!!!!
 
You are a great help !! i did every step you posted, got a little nervous bc I lost my connection to the VM and couldn't get logged in but managed to figure it out! Whats next ?? lmao
If you lost your connection to the virtual machine, it is usually because you removed the allowance for port 3389 (RDP). Glad you got it back though.

Next steps really depend on where you are in the process. In general, once you have access to the computer and you have set up the software, the next step is to punch holes through the firewall and the AWS security group for PMs ports.

As I mentioned before, setting up a secure (https) connection and registering your own domain are more advanced steps.
 
If you lost your connection to the virtual machine, it is usually because you removed the allowance for port 3389 (RDP). Glad you got it back though.

Next steps really depend on where you are in the process. In general, once you have access to the computer and you have set up the software, the next step is to punch holes through the firewall and the AWS security group for PMs ports.

As I mentioned before, setting up a secure (https) connection and registering your own domain are more advanced step
Everything seems to be working right now, I have new tables and cards in play. Yes, next steps were trying to figure out how to use my domaine name, SSL cert and what not. What ever happened it changed the public dns address ? I think thats what it is called, for the remote desktop log in.
 
Everything seems to be working right now, I have new tables and cards in play. Yes, next steps were trying to figure out how to use my domaine name, SSL cert and what not. What ever happened it changed the public dns address ? I think thats what it is called, for the remote desktop log in.
If you rebooted the machine, it would have gotten a new IP address. That also could have prevented you from logging back into it.

You'll definitely want to assign it an elastic IP. You can search through this thread to find some screenshots and examples of how to do that.

Same thing with your domain. Search through this thread for how to create an SSL certificate for your domain and how to set it up.
 
If you rebooted the machine, it would have gotten a new IP address. That also could have prevented you from logging back into it.

You'll definitely want to assign it an elastic IP. You can search through this thread to find some screenshots and examples of how to do that.

Same thing with your domain. Search through this thread for how to create an SSL certificate for your domain and how to set it up.
I know I hit the refresh button when I did those settings in AWS.. So anyway, the IP that i have been using to get to my Mavens poker site is (Example 00.123.33.124) but it has to have (00.123.33.124:8087) which is the file port in the system settings attached to the end of the IP ..I don't know if this is correct but it works. Did I do something wrong someplace ? I followed all your links that you shared with me step by step and everything is working. Thanks again for your help !
 
I know I hit the refresh button when I did those settings in AWS.. So anyway, the IP that i have been using to get to my Mavens poker site is (Example 00.123.33.124) but it has to have (00.123.33.124:8087) which is the file port in the system settings attached to the end of the IP ..I don't know if this is correct but it works. Did I do something wrong someplace ? I followed all your links that you shared with me step by step and everything is working. Thanks again for your help !
I saw this in the other forum (If you are not going to run an IIS web server on your AWS account then you should change your File Port setting in Poker Mavens to 80. Otherwise you will have to include the port number on the end of your domain (such as www.example.com:8087). Should I add port 80 and 443 in AWS and then change settings in the mavens system setting file port or packet port? I am pretty sure I know how to do that. I know I want to end up using my domain name to give out as reference to the game and not an IP address.
 
I saw this in the other forum (If you are not going to run an IIS web server on your AWS account then you should change your File Port setting in Poker Mavens to 80. Otherwise you will have to include the port number on the end of your domain (such as www.example.com:8087). Should I add port 80 and 443 in AWS and then change settings in the mavens system setting file port or packet port? I am pretty sure I know how to do that. I know I want to end up using my domain name to give out as reference to the game and not an IP address.
Yes, you should. "http" by default is port 80 and "https" by default is port 443. So, https://www.pokerchipforum.com is the exact same thing as https://www.pokerchipforum.com:443.

Since this is the only web server you are running, it's totally fine and acceptable to change your ports to the standard 80/443. You will need to:
In my example images here, I've added port 443 to AWS (since I only care about https) and I've added it to the windows firewall as well:
Screen Shot 2020-04-20 at 3.25.51 PM.png


Screen Shot 2020-04-20 at 3.26.48 PM.png
 
Yes, you should. "http" by default is port 80 and "https" by default is port 443. So, https://www.pokerchipforum.com is the exact same thing as https://www.pokerchipforum.com:443.

Since this is the only web server you are running, it's totally fine and acceptable to change your ports to the standard 80/443. You will need to:
In my example images here, I've added port 443 to AWS (since I only care about https) and I've added it to the windows firewall as well:
View attachment 848764

View attachment 848769
Yes, you should. "http" by default is port 80 and "https" by default is port 443. So, https://www.pokerchipforum.com is the exact same thing as https://www.pokerchipforum.com:443.

Since this is the only web server you are running, it's totally fine and acceptable to change your ports to the standard 80/443. You will need to:
In my example images here, I've added port 443 to AWS (since I only care about https) and I've added it to the windows firewall as well:
View attachment 848764

View attachment 848769
I am going to have to get your paypal or venmo when I am all done with this ! haha.... Thank you ! you are extremely helpful and obviously have a ton of knowledge !!
 
So I added AWS inbound rule ports 80 and 443. Did the same in windows firewall wall on VM for mavens, then changed file port to 443 in mavens system and when i put IP address in address bar I cannot connect. if I change the file port back to 8087 on maven system I can connect but with :8087at the end of IP address . Im a bit confused
Screen Shot 2022-01-19 at 1.57.14 PM.png
 
So I added AWS inbound rule ports 80 and 443. Did the same in windows firewall wall on VM for mavens, then changed file port to 443 in mavens system and when i put IP address in address bar I cannot connect. if I change the file port back to 8087 on maven system I can connect but with :8087at the end of IP address . Im a bit confused View attachment 849017
I'm assuming that you have not yet created an TLS certificate for https connectivity; this means you're restricted to plaintext and that PM will run only plaintext http on port 80. So, you should try http://your-server instead of https://
 
I'm assuming that you have not yet created an TLS certificate for https connectivity; this means you're restricted to plaintext and that PM will run only plaintext http on port 80. So, you should try http://your-server instead of https://
haha.. you are correct ! i didn't know that mattered, TLS is same as SSL correct ? I am getting SSL now
 
haha.. you are correct ! i didn't know that mattered, TLS is same as SSL correct ? I am getting SSL now
Yes, for the normal person HTTPS = SSL = TLS ... I'm not going to go into the distinction between them b/c it's not necessary and will only confuse people more. I write TLS instead of SSL since I'm a software engineer and that's what is "correct" nowadays.

Anyway, the process for getting a certificate so you can do HTTPS is as follows:
  1. Purchase a domain (chopspokersite.com)
  2. Decide on your subdomain (www, play, etc) ... this will become your URL. For example if you pick "www" for your subdomain, you'll get www.chopspokersite.com as your final address. If you chose play, it would be play.chopspokersite.com.
  3. Purchase a certificate for your site. The certificate will be for your site named above (ie www.chopspokersite.com). Most people choose Comodo since they are dirt cheap. Comodo will ask you a bunch of questions, and then you'll need to prove you own the domain chopspokersite.com. This is usually done by them emailing you at admin@chopspokersite.com and then you paste in the special code they emailed you.
  4. Download the certificate files to your EC2 instance, and then configure PM to use them
  5. Don't forget to associate an Elastic IP address for your EC2 instance. That way, www.chopspokersite.com will always be the same IP address.
And, yes, HTTPS means you MUST have a domain name. You cannot purchase an SSL/TLS certificate for an IP address; it has to be for a domain.
 
Yes, for the normal person HTTPS = SSL = TLS ... I'm not going to go into the distinction between them b/c it's not necessary and will only confuse people more. I write TLS instead of SSL since I'm a software engineer and that's what is "correct" nowadays.

Anyway, the process for getting a certificate so you can do HTTPS is as follows:
  1. Purchase a domain (chopspokersite.com)
  2. Decide on your subdomain (www, play, etc) ... this will become your URL. For example if you pick "www" for your subdomain, you'll get www.chopspokersite.com as your final address. If you chose play, it would be play.chopspokersite.com.
  3. Purchase a certificate for your site. The certificate will be for your site named above (ie www.chopspokersite.com). Most people choose Comodo since they are dirt cheap. Comodo will ask you a bunch of questions, and then you'll need to prove you own the domain chopspokersite.com. This is usually done by them emailing you at admin@chopspokersite.com and then you paste in the special code they emailed you.
  4. Download the certificate files to your EC2 instance, and then configure PM to use them
  5. Don't forget to associate an Elastic IP address for your EC2 instance. That way, www.chopspokersite.com will always be the same IP address.
And, yes, HTTPS means you MUST have a domain name. You cannot purchase an SSL/TLS certificate for an IP address; it has to be for a domain.
I bought a domain, lets call it "chopspokersite.com" and I bought an SSL all on godaddy (a bit pricey but none the less I have it). I downloaded "private key" file and another file called "generated-csr.txt" .. as far as certs are those the ones I need, I did this before adding a subdomain, hopefully that does not matter? So I am in the DNS part of godaddy at the momonet. The elastic IP was already done, I believe it was done with your previous instruction "elastic ip" Screen Shot 2022-01-20 at 6.18.19 AM.png
 
Your graphic looks correct. You're creating an "A" record for your subdomain to point to your elastic IP, which should be the same IP that poker mavens is showing you. If poker mavens is showing you a different IP address, you might need to stop the server and restart it for it to pick up the new elastic IP address.

Before you can start with your server, you'll need to follow the instructions here to download OpenSSL and place it on your server so that poker mavens can start up and find it:
https://www.briggsoft.com/pmfaq.htm#q17

And finally, this is an example of how the configuration of poker mavens will look with the certificate files that you download from GoDaddy:

1642682988190.png
 
Your graphic looks correct. You're creating an "A" record for your subdomain to point to your elastic IP, which should be the same IP that poker mavens is showing you. If poker mavens is showing you a different IP address, you might need to stop the server and restart it for it to pick up the new elastic IP address.

Before you can start with your server, you'll need to follow the instructions here to download OpenSSL and place it on your server so that poker mavens can start up and find it:
https://www.briggsoft.com/pmfaq.htm#q17

And finally, this is an example of how the configuration of poker mavens will look with the certificate files that you download from GoDaddy:

View attachment 849208

Your graphic looks correct. You're creating an "A" record for your subdomain to point to your elastic IP, which should be the same IP that poker mavens is showing you. If poker mavens is showing you a different IP address, you might need to stop the server and restart it for it to pick up the new elastic IP address.

Before you can start with your server, you'll need to follow the instructions here to download OpenSSL and place it on your server so that poker mavens can start up and find it:
https://www.briggsoft.com/pmfaq.htm#q17

And finally, this is an example of how the configuration of poker mavens will look with the certificate files that you download from GoDaddy:

View attachment 849208
I don't know what the "root certificate file" is ?but I think the other stuff is right. and if change to {yes} for encryption it says "could not load ssl" I am going to have to walk away from this for a while.. this is to hard and frustrating. Thanks again for all your help

sslpic.PNG
 
Last edited:
I don't know what the "root certificate file" is ?but I think the other stuff is right.
If you tell us what files go daddy gave you, we can tell you which ones go where. Yes, it looks like the private key file is correct, but the certificate is wrong. The file that you have there is the CSR which is the signing request not the actual certificate.
 
If you tell us what files go daddy gave you, we can tell you which ones go where. Yes, it looks like the private key file is correct, but the certificate is wrong. The file that you have there is the CSR which is the signing request not the actual certificate.
I will try and download from here ? I dont think I ever did this and the only thing I have right now are the 2 you see in the PM system. Just not sure what the server type is that I should select ? Actually I am guessing "OTHER" as on the Instruction page AWS falls under other, is that correct ?

Screen Shot 2022-01-20 at 9.59.26 AM.png
 
Last edited:
Yes, I think that Other should work (Apache would probably work too, but let's try OTHER)
This is what is in the zip file which I have downloaded on the server/VM. So I just extract all and then I should be able to put the paths in on PM System correct ? I did delete what was already there so I could just start over.


Screen Shot 2022-01-20 at 10.41.56 AM.png
 
I believe gd_bundle-g2-g1.crt is your "root", the other crt is your regular certificate file and the pem is your key.
 
That is because you missed my point above where you need to download open SSL and put that on your server. It's because they are not allowed to ship it as part of their software.

https://www.briggsoft.com/pmfaq.htm#q17
I am still confused. I had to walk away from this last night. It says .."Instructions for creating a Certificate Signing Request file are available on the Utilities page. You will also need to put the required OpenSSL 32-bit DLL or 64-bit DLL (for 64-bit Gold edition) files into the program folder where PMServer.exe is installed" are these the two .dll files that are in the SSLcert100 folder that read libeay32.dll and ssleay32.dll ? below are the files I have that csr created and what I have from godaddy.
Cert100file.PNG

Screen Shot 2022-01-20 at 10.41.56 AM.png
 
I am still confused. I had to walk away from this last night. It says .."Instructions for creating a Certificate Signing Request file are available on the Utilities page. You will also need to put the required OpenSSL 32-bit DLL or 64-bit DLL (for 64-bit Gold edition) files into the program folder where PMServer.exe is installed" are these the two .dll files that are in the SSLcert100 folder that read libeay32.dll and ssleay32.dll ? below are the files I have that csr created and what I have from godaddy.View attachment 849836
View attachment 849837
I can't figure out where or how to get the files and file paths to insert into PM system
 
@BearMetal is DA MAN! No way I would have got my site up and running last year without him.
Some people run awesome GBs (like you), others can rattle off perfect tournament breakdowns for any number of tables. Me? I help out PCF members who wanted to continue playing online when the world shut down. Just my way of being a part of the community.

Oh, and I make some pretty cool 3D poker prints :D
 
Some people run awesome GBs (like you), others can rattle off perfect tournament breakdowns for any number of tables. Me? I help out PCF members who wanted to continue playing online when the world shut down. Just my way of being a part of the community.

Oh, and I make some pretty cool 3D poker prints :D
Yes you do make some cool 3D stuff. We need to talk.

(see what I did there - buttered you up first with a compliment - :D )
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account and join our community. It's easy!

Log in

Already have an account? Log in here.

Back
Top Bottom