Hopefully someone can help because I'm hitting a brick wall here! :)
I have setup an apache web server at home and I have installed wordpress.
I also have my own domain and a dyndns account, I have repointed a dyndns record to my hostname on a different port.
When I navigate to my website it works fine however if I don't enable cloaking on dyndns it shows my hostname. I don't really want this as I want it to display only my domain name.
If I enable cloaking on dyndns to use my domain url wordpress sort of works however if I click on Log in to get to my control panel I get a blank page as its trying to navigate to my hostname:port
Please could someone point me in the right direction? I'm sure their must be a way to do this!
Thanks in advance
Dan
I use Dyn to manage my Domain and DNS, but I had never used their WebHop feature before. I checked it out and, unfortunately, I don't think it will produce a completely transparent proxy for WordPress as you had hoped.
The problem is that "When Cloaking is enabled on a WebHop, frames are used to mask the address and title bars." (ref: here). If you define a cloaked WebHop for blog.example.com that redirects to http://yourhome.dyndns.org:8080/wordpress/ then the page that appears "belongs" to blog.example.com but displays content from the actual host inside a frame
<frame src="http://yourhome.dyndns.org:8080/wordpress/" name="redir_frame" frameborder="0"
scrolling="auto" noresize="noresize" marginheight="0" marginwidth="0"/>
The frames are messing you up when you click on a link. In your case you get a blank page, but under IE9 I see
If in your WordPress settings you have "WordPress Address (URL)" set to http://yourhome.dyndns.org:8080/wordpress/ then clicking the "Open this content in a new window" link will work, but you've lost your cloaking. If you try to preserve the cloaking by changing the "WordPress Address (URL)" to http://blog.example.com then your WordPress site won't work correctly either.
So, I think you'll have to choose between:
Using a WebHop and exposing your actual hostname/port (at which point cloaking becomes something of a moot point), or
Looking into setting up a reverse proxy on another server to redirect traffic to your "home site" and map the links back to the proxy (for complete transparency).
Related
I have a domain name from NameCheap, and I am hosting a WP site on Amazon Web Services EC2. I have already changed the A record to so the site pulls up anytime i go to myDomainName.com. Everything works fine until I hit the home bottom on the website. At that point the IP comes up in in the address bar. Any pages i access after that will have the IPaddress/page.
I know I may need to change something in the wp-config.php, but I don't think I have this file on my computer (I used AWS to launch WP, and I don't think I have download anything about WP except some plugins). My website address change option in setting-general on WP is also greyed out so I cannot change it. Anyone has any idea how I could make my domain name display?
Any help is appreciated. Thank you so much!!
have you tried changing your home and site url in wp-admin? If you go to wp-admin/options.php you can change the home and site url fields to your domain name. You can also do it through phpAdmin or editing the DB directly (wp-options table).
Could you help me find out what to do with not fully secure message.
I have installed ssl certificate from let's encrypt, but my wordpress homepage has a message "Attackers might be able to see the images you're looking at on this site and trick you by modifying them".
The home page is still in development, with demo content. About what images chrome notification is telling? Something to do with cookies?
Thank you for your answers!
Edit: Does it have to do with the theme itself? Whole wordpress dashboard and login is served over proper secure ssl.
Sending images via http protocol is what triggers this issue. Using any content from a cdn that does not use https will also trigger this issue. This quote explains it pretty simply (the yellow padlock / warning of unencrypted content/images):
If a yellow padlock appears with a mini yield sign, the likely cause
is links in your site still refer to an unsecured page. Make sure that
all your images, menu items and links use https in the URL.
source
I would use a tool to help identify all non-encrypted file transports. One such tool would be something like Why No Padlock.
Did you enable https after installing WordPress? If so, you must change the WordPress address and Site Address under "General Settings" in WordPress. Make sure both addresses use https.
If your WordPress site address is set to use http, your server will force https but WordPress will serve certain images, like the favicon, over http. This triggers a "mixed content" warning.
I too had run into this issue. It appears there are many http: that need to be replaced with https:
You typically do this using a plugin called Better Search and Replace. Make sure you are adding colon (:) at the end of both http and https.
I found a working answer here
To check for issues on the chrome/opera inspection console (ctrl+shift+C) is also a great idea: I had setup all correctly and the issue was the footer image, not something you would check very often looking for this fix. I had applied SSL to many websites, sometimes the issue is just one simple link and this method helps find it.
I had the same problem where the home or index page was saying the page was not fully secure "Attackers might be able to see images blah blah blah"
After enabling https in general settings under site address and wordpress address I was still getting the insecure image warning on the index or home page.
The next step was to find out what images were not using the https ref on the index or home page.
In my case I viewed the page source of the page, by right mouse clicking the page in the chrome browser & looking for images url ref which were still showing http. I was using a sliding header and those images were showing http. So all I did was go into slider header in the appearance menu of the wordpress, and re-assign each of the header slider image for each frame. RE-checked the home page now the image urls were showing https. Bingo the secure lock symbol returned.
Obviously these image urls don't get updated via the general settings... which seems an oversight by whoever wrote the part of the word-press script.
I have a domain residing with one organisation for managing DNS and a wordpress site built as a sub-domain of another site of mine.
I set up web forwarding, expecting the domain to be reflected in the address bar for site visitors, but the sub-domain is showing instead.
i.e. www.domain1.com should forward to subdomain.domain2.com and show www.domain1.com in the address bar. Meanwhile, my www.domain2.com should still render the other wordpress site I have there.
Am I right in thinking I need to do this through my htaccess file? If so, can anyone advise on the syntax I need to use to do this? I can currently only find information on mapping a sub-domain to the www of the same domain.
Thanks in advance :-)
This comes down to the provider's definition of "web forwarding", which is a vague marketing term. It sounds like they're just doing a straight redirection unfortunately, which no amount of playing with .htaccess files can fix: you simply cannot make a website tell the browser to stick another domain name in its address bar.
What I'd suggest is talking to them and see if they can do a CNAME for www.domain1.com to subdomain.domain2.com, or switch to it using the same IP address instead. You will then need to set up your Wordpress install to respond to "www.domain1.com" requests.
do you have control panel for your domains?
Im using direct admin and they call it "domain pointers" - I believe it does exactly what you need.
You need to create alias for your subdomain.domain2.com which will point (not forward, if you forward it also url in browsers address bar will be changed) www.domain1.com to the subdomain.domain2.com without url change.
If you are not using any control panel, you need to create alias manually by adding same dns for your www.domain1.com (no matter A or CNAME) as it is for subdomain.domain2.com AND in server configuration set response for www.domain1.com (ie. apache servername and serveralias, in iis binding)
I dont think .htaccess is a good idea for achieving what you described.
We recently went from http://www.example.com to https://www.example.com to allow for a more secure online environment. This was done partly to allow for on-site donations.
We utilize a social sharing tool called ShareThis (www.sharethis.com). Our home page has received several thousand likes and "ShareThis" clicks over the past year. Unfortunately all of these are now gone when changed to https.
Is there a solution to this issue?
I see two options:
1) Change from https:// back to http://
2) Ask the company to update your website in their database and/or update their software to recognize that http://www.example.com and https://www.example.com are the same website.
So, those are two options if you're willing/able to switch back to http://, otherwise, omit option 1.
You can customize the URL that you pass to the widget. Pass it the http URL so that is what will get shared and that's the counts you will get..
I wrote the ShareThis widget so let me know if this works for you..
Our company is trying to transition to WordPress Multisite but we have several issues working against us at the moment. We host WP outside our server environment (we use Amazon for our WP sites) so we actually have to use an URL proxy to our Amazon servers. The other issue is that we needed to install Multisite in the root of the folder so the domain is http://100.10.20.30/foldername but we can't proxy that to http://www.domain.com/foldername because that is a live site that we're not moving to WP any time soon. So, of course, the problem we're running in to is that the IP is showing up not only in the source code but in Google now as well (which we don't want).
Does anyone know of anything we can do to keep the IP out of the source code/Google? I was thinking about rewrite rules in the htaccess file but didn't want to do anything until I had some better ideas.
Also, I can't use the domain mapping plugin that everyone seems to suggest for this type of issue because our sites aren't hosted in the root of our server (a prerequisite for the plugin).
So to break it down, this is what we need:
Multisite Parent Blog <-- This has to be the IP address
Multisite child blogs <-- Domain name but when we set the actual proxied domain name in the settings we get a 404 error because it's not looking in the right place. It's looking for an actual folder on our internal servers.
Thanks!
Found the solution myself. Posted below:
In the Multisite dashboard, click on "All Sites" then administer the specific site.
Under the "Path" field, you'll need to deselect the "Update siteurl and home as well."
Save changes.
Click on "Settings" tab.
Change the URL in the following fields: "SiteURL" and "Home"
Save changes.
When all is said and done, the IP is showing in the "Info" tab but it changes the URL in the source code to your domain.