Setup Wicket application/JBoss Server to use my domain URL - jboss

I just purchased a domain Url from Google Domains and I'd like to have my localhost project (Wicket app. deployed on Jboss server) to use my new domain (example.com). I have looked online for a process on doing this, but seeing as this is a very specific instance, I cannot find the proper documentation. I have made my ip addr. static, added my external IP addr. to the Google Domain website (I think this registers my domain to my ip?), and I've edited the Window's Host file to point 127.0.0.1 to example.com. What am I missing here? Is there a configuration in my wicket project's web.xml or maybe a configuration in my JBoss server? I'm using Wicket 7.0.0 (latest) and JBoss 7.0. Any help would be greatly appreciated! Thanks in advance!

I am not an network expert, but you could check if you are receiving any traffic on your JBOSS server port without application deployed, just to make sure that your firewall or any sort of Antivirus is blocking incoming traffic or not.

Related

Hosting two different servers with one domain

I'm trying to host web pages using Win Server 2016. Currently, I have Jira and my personal web (IIS) servers. Using AWS, I currently have "myec2.com:port1" and "myec2.com/port2" running fine. And I'm planning to buy a domain "myname.com" to be connected to "myec2.long.name.com"
What I hope to do is "myname.com/jira" and "myname.com/mypage" or "jira.myname.com" and "mypage.myname.com" can redirect to Jira server and the IIS server. Is there a way I can achieve this goal?
Thanks in advance.
If you buy a domain like myname.com you will be able to configure any number of sub-domains such as jira.myname.com or mypage.myname.com as you like.
Usually what you would do is point those sub-domains to your server's IP then handle requests to those domains by setting up a web server (like apache or nginx) and configuring a virtual host (apache) or a server block (nginx) for each one of those sub-domains.

Hosting WCF REST Service as a child application in IIS

I am trying to host a WCF RESTful service in IIS as a child application under and existing Site but it will not work. It works fine when I host it as a Site by itself, but the problem is that both Sites share the same port numbers, port 80 (http) and port 443(https). Can anything help with how to get around this?
You must select the default site, do right click and add application or create a virtual folder to point to default folder where your service is in dev...
If you choose the first you need to create a file system of the service, with publish in Visual Studio.
and
.
So with this approach you can use the same port with different route.
Thank you for for taking your time to answer the question. I was able to get the solution myself. It was because I did not configure HTTPS when I hosted the service in IIS. After I configured the HTTPS, everything works great.

Drupal IP/domain redirect

I recently redid a client's old Drupal site, in Apostrophe, and pointed their domain to the new server.
I am now trying to access the old site via IP address, but there seems to be a redirect configured to rewrite the base IP address to the domain name (72.xx.xxx.xxx to www.clientdomain.com).
Is there something configured in Drupal to rewrite the IP address? Can I change a field in the database or configuration files to prevent this?
I have ssh access to the server, and have poured over the Drupal code, settings.php, .htaccess, etc., but cannot locate this offending field. I am not familiar with Drupal, but suspect it could be an admin setting. Since the site redirects, I am unable to login to the admin backend.
Any and all insight is appreciated. Thanks for your help!
A few possibilities:
In the settings.php (sites/default/settings.php), see if there is a $base_url set. If you can see any, comment that line. You can run a drupal site without the base_url hardcoded in the settings.php
In the .htaccess look for redirects. Your safest bet is to replace it with a fresh file downloaded from http://drupal.org/project/drupal
The most likely case is that your web server is configured to redirect the IP address to the main domain.
You can also access your site at old server by explicitly setting the IP address in your hosts file. Check it for your operating system DNS resolver docs.

Setup SmarterMail on IIS as subdomain

I am surprised there is not more information out there about this. I assume it is a fairly common issue.
My situation: I have a vps that I have setup a website on (http://honeybadgertech.com/) and I would like to add email also. Preferably on a subdomain such as mail.honeybadgertech.com. I have done the basic installation of smartermail but cant find instructions on how to configure it to run on IIS as a sub-domain. I have setup many websites in the past but I have no experience with email at all. Can anyone help me with the details of setting up smarter mail on a sub-domain? or would it just be easier to register a separate mail domain from godaddy to run the email?
Ok so here is how I was able to get running.
Install download
Setup sub-domain in IIS
Add A or CNAME Record for sub.yourdomain.com
Add MX Record for yourdomain.com
Add reverse DNS record (if possible)
Hope this helps someone!
You can make the following changes in IIS to access the mail.domain.com.
Start >> Administrative tools >> IIS.
Select SmarterMail Website.
Click on Bindings. Add new binding with port 80. (By Default Smartermail runs on the 9998 port)
In the host header value box, add mail.domain.com.
Click Ok.
Now, you can access the SmarterMail with http://mail.domain.com in your browser.

Run ASP.NET in wamp server

Is it possible to run an .aspx website in WAMP Server? If yes, then how do you do this? Please reply
It used to be possible to have Apache interface directly with the ASP.NET engine/system via mod_aspdotnet, but that module was abandoned some time ago.
The way you do this now is to have Apache be the front-end server (port 80) and have IIS be the back-end server (8080). Then use Apache's ProxyPass directive to proxy specific websites or URLs to IIS, which runs the ASP.NET code, and give the output back to Apache, which delivers it to the visitor/client.
It's not a bad option and works well.
You just have to make sure you're either running Apache and IIS on different IPs, or same IP but different Ports.