I hava a website, and deploy the site on nginx in docker container. The proplem is when I refresh the site the chrome address bar brings out the port number and redirect wrong.
I am a front-end progromer and don't hava any server permission. so i can try nothing on back end. On the server side already tried nginx config file but nothing help.
This is the website address:
www.haetek.com/case
If you refresh brings out port number 8181.
www.haetek.com:8181/case
I expect normal address redirect.
This qustion is solved just add a slash at the end of the address,
this address
www.haetek.com/case
to this address
www.haetek.com/case/
I don't know the detail why it solved the problem. but it worked.
Related
Just trying to set up SSL https for my site, using the Bitnami Tool bncert-tool. It shall automate the SSL setup by naming the domain. Unfortunately, I get the message
Warning: The domain 'mypage' does not resolve, please fix its DNS entries or remove it.
Press [Enter] to continue:
Thing is, I can get to the page via domain name and the IP. So no Problem on that side.
I have no clue! I have set up an elastic IP in EC2 and connected the domain in Route53 by adding the dataset. Has some faced the problem before and cases.
From the warning message, 'mypage' is not a domain. Actually have to enter in the full domain path such as
www.google.com
or
google.com
Good luck.
I've got EC2 Amazon Linux 2 instance with apache, mariadb and wordpress
VPC, Security group, ACL are set up correctly, i'm using same rules for other websites and works perfectly
telnet ip 443 and telnet ip 80 - both are reachable, checked and connected
I don't have access to DNSes, so I changed windows host file. Both are pointing to the same ip.
x.x.x.x example.com
x.x.x.x example.sandbox.com
ping recognize both and showing that there is no issue with host file.
First website with SSL.
Second website without SSL (tests purposes).
They are using same database but different schema. So table
wp_options and value for home and siteurl are set up correctly for
https://example.com for first one and http://example.sandbox.com for
test one.
First website is working fine, showing example.com with SSL. Nothing to do. Problem is with test environment. Everytime I try to reach example.sandbox.com chrome first shows me warning that page is not secured (expected) and after that redirects me to example.com. Same with Firefox. After added exception it redirects me to example.com. I run out of ideas...
Apache configs in comment. Have no idea how to paste it into post without error. Spent hour on it...
Found it!
Wordpress plugin really-simple-ssl. Removed it and it works.
I have Xampp setup on my windows machine, with a WordPress site, when accessing it, through localhost, it runs normally, however after I linked my computer, through no-IP, for a dynamic DNS, and attempt access through the internet using the hostname, I get prompted for a username and password for some reason.
I'm not sure why this is happening.
I realized I didn't forward a port so it was actually redirecting to my router page and asking for username and password.
Anyhow, I found this YouTube video on how to forward a port for linksys router: https://www.youtube.com/watch?v=pIK-RpVNAM8
Didn't realize it was more of a Network question.
We have deployed our website to the live webserver, Windows Server, IIS 7.5. Website asp.net, .NET 4.5
I have configured the website bindings to allow https requests for this website.
Asked the hosting provider to open up the port 443.
I can access the website over internet with port 80, no issues at all. (http://mysite.com)
But I can not access via https, (https://mysite.com).
But I can access the site via SSL from the server itself, that means SSL configurations are fine.(https - localhost)
But I can telnet (telnet mysite.com 443), it responds to GET request via telnet.
I have rechecked the certificate and changed it to a self-signed certificate, issue is still there.
These requests not being tracked in IIS logs as well, seems like the request is not reaching IIS. Hopefully something goes wrong before it reaches the server.
But, when I access the website as http://mysite.com:443, it works.
I m bit confused with this behaviour. Obviously the port 443 is open by the hosting company. But something is wrong with requests over HTTPS, which is supposed to send a request to port 443. Please help.
Because your site is working when you access http://mysite.com:443, I am almost sure that you created wrong binding on IIS. Instead of selecting https from combo box you selected default http.
There is a tutorial on how to do this on youtube: Changing IIS 7.5 Bindings by David Johnson
You've establish that the port is open and the hostname binding is there, otherwise http://mysite.com:443 would not work. Its the SSL part that's not working, hence you can connect directly by port and telnet (port 443 but not SSL) but not a browser via https. It's only a browser connecting to a https url that will expect SSL.. I'm pretty sure I've had the same issue, but cannot recall the exact cause but it was definitely related to an invalid SSL configuration or SSL binding.. The behaviour was like there is no connection, nothing, which is unusual, its the bad config causes the browser to abort the connection. If I remember what, I'll update or comment below.
So you can access the site using https://localhost? Your question is not quite clear on this point... what is the exact URL you are using? If it's https://localhost, that is actually an indication that your certificate is configured incorrectly. You seem to be interpreting this as an indicator that it's working OK and that is not the case. The domain name is tied to the certificate and SSL will work only when accessing the site using that domain name. So if it works for "localhost", something is wrong.
Finally I found the solution. Issue was a setting in the load balancer of the hosting provider. I have asked the question from them and they have figured out the issue. Anyways it was a good learning curve for me. And this knowledge is going to help others.
The firewall was already allowing both HTTP/HTTPS, which is why we could telnet through and run a GET / and still pull down content from the 404 page of the IP address.
It appears there was a certain profile applied to the HTTPS configuration in the load balancer which would only work for HTTP, so they have disabled that.
When they set this up for HTTP and HTTPS they were not able to test HTTPS, because to do so would require an SSL certificate in IIS - which it appears we have already provided.
Thanks everyone for your help on this!
I move my wordpress from my server to my localhost in the database I change
http://www.hybrid-tech.net/praxi3 to http:// localhost:8888/praxi3
after that, when I try to see the website on my localhost I go to
http:// localhost:8888/praxi3
but it's redirect me to
http:// localhost/praxi3
and I'm don't understand why. I back up a restore many times this database and I still getting this problem.
Thanks in advance for your help.
PD: I'm using mamp. The localhost link are without the space I mean http://lo....
You should check your mamp configs :
Is your apache port set to 80 ? If so the server redirects you to the 80 (default web port)
Try setting it to the 8888 port and refresh your page using the flush cache command :
ctrl+r or apple+r