0

I own a domain in godaddy (rainychat.com), and i have a node/socket.io chat app hosted in openshift on a domain provided by them (rainychat-jgal.rhcloud.com)

I'm using "forwarding with masking" configuration on godaddy to make it so when a user enters rainychat.com, godaddy forwards the user to rainychat-jgal.rhcloud.com, but with the user seeing rainychat.com in the browser (You can try that now if you want).

Forwarding config My question is: As this is a chat app, is the user constantly going through godaddy first to reach my app because of the masking? I don't want my app to be slower because of this configuration. Is this the correct way to permanently direct a user to the site while still showing rainychat.com in the browser, or should i mess with DNS registery? Can i use .htaccess maybe?

user5869120
  • 121
  • 1
  • 9
  • Yes, this is most likely a "reverse proxy" which publishes the content "through" your frontend server. This is indeed an extra step, or hop from a network point of view. But typically the difference should be extremely small, I would not bother about that too much. – arkascha Apr 08 '16 at 18:51
  • How would i go to avoiding the extra step? I'd like to avoid any delay if possible – user5869120 Apr 08 '16 at 19:15
  • Then you cannot use the proxy step. That would be possible if you operate the systems yourself, since you can then alter the host definitions. But such thing is impossible if you are just using a hosting provider. Then you have to play to his rules. So you end with your users not getting shown your domain, but a generic domain name of the hoster, if that is possible at all. – arkascha Apr 08 '16 at 19:20
  • I'm currently trying to set this up as well for my OS app. I set up a cname record and sort of got it working. However, I now get a ssl cert error because I'm on a free account. I could upgrade but won't for now. Do you have your own ssl cert? I switched back to forwarding now. – fat fantasma Apr 08 '16 at 22:06
  • No ssl, sorry. So, which is better? 1) Forwarding with masking. 2) Forwarding + .htaccess file for the masking. 3) Mess with DNS records directly – user5869120 Apr 08 '16 at 22:53
  • Like I said, Im right in the process now. I just switched to forwarding with masking but getting an error from OS. Everytime I make a change it takes about 30 minutes to take affect. Very slow going. I don't think your #3 is going to give you desirable results with an ssl cert. – fat fantasma Apr 08 '16 at 23:03
  • My forwarding with masking just updated and works now. I am going to try an experiment and see if I can get the cname working without an ssl cert next – fat fantasma Apr 08 '16 at 23:10
  • To clarify, I can get the cname working but chrome gives and cert error when visiting my OS app. Looks bad and scary for people to visit and trust. I will see if I can work around it and report back. – fat fantasma Apr 08 '16 at 23:19

0 Answers0