I am setting up a corporate intranet site using WAMP and wordpress. I have a server running IIS on port 80 and WAMP on port 8080. I have the wordpress site running under WAMP. I want to publish the wordpress site without the port number.
For example, http://MyServer/MySite rather than http://MyServer:8080/MySite.
I have tried leaving the port number out of the "Site Address (URL)" but that doesn't work.
You need to reverse proxy it in iis
you need to install URL rewrite and Application Request Rerouting ( both MS plugins )
Then make a virtual directory under your main site (at the location you want "MySite" ), and go to url rewrite and it has an option to create the reverse proxy.
This will also mean you get HTTPS if your main site has HTTPS already
and reverse proxy to where your WAMP is hosted on your server
Related
I recently migrated from HostGator to AWS. Everything has worked, including the SSL. This happens on all browsers. Here is what I have setup: (Screenshots attached)
An EC2 instance that's running the WordPress AMI and has an Elastic IP assigned EC2
ACM for both domain.com and www.domain.com, verified by DNS on Route 53 ACM
Target Group with port 80 and HTTP protocol being targeted to the EC2
instance Target Group
Load Balancer listening to port 80 and 443 both forwarded to Target Group Load Balancer
Route 53 with the A record using the Load Balancer as an alias Route 53
CloudFront with domain.com as origin domain name(www.domain.com as CNAME), protocol of "Match Viewer", and connected to the ACM certificate CloudFront.
What would be causing the error? Where should I start looking?
Check URL settings via Administrator Dashboard
or change the URL from wp-config.php
simply add these two lines of code there
define('WP_HOME','http://example.com');
define('WP_SITEURL','http://example.com');
3. or check deactivating all plugin, anyof plugin maycauing the issue
or try using Simple SSL plugin.
I want to configure Wordpress site (http://example.com/blog ) served from Apache. Webapp using Tomcat on same server listens on port 8080. These need to be redirect from 80 to 8080.
I tried reverse proxy method but was not successful.
Look at the wordpress configuration:
See table wp_options, there are two options:
1. siteurl
value: http://yourhost:port/
2. home
value: http://yourhost:port/dirname/
When you install the wordpress, the two paths above was set to the database, so if you change the port, it won't change it self, you should change it manually. Or it will always trigger a redirection there.
I have domain setup like http://www.example.com/in which is a wordpress multisite setup and hosted on a AWS EC2 instance.
I have to make another similar setup with url http://www.example.com/uk but on another EC2 instance.
The domain www.example.com is routed to only one IP of first instance.
Can anyone advise on how I should setup this routing to make this scenario on Amazon Route 53?
Assuming you are serving your site using apache you can add a .htaccess rule on the instance hosting www.example.com to redirect www.example.com/uk traffic to another ip address.
This will mean you rely on www.example.com to redirect traffic for www.example.com/uk. In the event the instance running www.example.com were to become unavailable, www.example.com/uk would become inaccessible.
Alternatively, you can setup a subdomain in Route53 with the following entry
uk.example.com 1.2.3.4
This will mean that www.example.com/uk will need to be accessed using uk.example.com not www.example.com/uk
I have a series of vhosts that work fine on global settings of port 80 set in mamp pro. One new vhost I created will not work though on this port. I type in my vhost in thew browser or even use the link provded and it appends a :8888 onto the link and says can't establish connection to server.
When I change that vhost port # to 8888 then it works.
The problem is the :8888 remains and is screwing up my url routing for navigating the site especially with a standard wordpress build, I cant get into my admin section bc wordpress donest understand the :8888.
Any ideas how to fix this issue with mamp pro?
First you need to change port to 80
Server->general Apache value to 80 then create vhost
in Host ->add new
Server name
ip/port you can add as *
then disk location
that it done !
I recently bought a domain. Let's say my domain is "domain.com", and I made a website in visual web dev. using ASP.NET and VB.NET. I also have an old computer that I turned into a home server so I installed windows server 2008 R2 SP2. So I uploaded my website to a folder and went to the IIS manager. There I added a website, set the sitename to "domain.com" application pool to "ASP.NET v4.0". Then the physical path to: "c:\websites\wwwroot\domain.com" then in the bindings I added 3 different things.
type hostname port IP adress
http www.domain.com 80 my IP found at www.what'smyip.com
http domain.com 80 my IP found at www.what'smyip.com
http *blank* 80 192.168.1.6(my server's internal IP)
I made sure port 80 is open in my router and I added a firewall inbound rule for port 80.
When I connect using 192.168.1.6 I get my website and everthing works like it should.
However when I connect using domain.com or www.domain.com I see a 404 page. http://prntscr.com/42ynf4
Also when I change my bindings and I change the IP for domain.com and www.domain.com like displayed below:
type hostname port IP adress
http www.domain.com 80 192.168.1.6(my server's internal IP)
http domain.com 80 192.168.1.6(my server's internal IP)
http *blank* 80 192.168.1.6(my server's internal IP)
It works just like it's supposed to?
I have done a DNSlookup on the domain and it's active. I'm a little bit stuck on this and I know you guys aren't experts on hosting but you all probably have more knowledge about this then I do.
You should check what is the server IP address (netstat), because you could use a proxy and then the Internet IP info will be not correct.
Also, make sure that you set the correct home page in IIS.