I am running Plone 4.1 on Ubuntu 10.04. How one should configure
Varnish (public IP:80) - default.vcl from Ubuntu/Debian
plone.app.caching
... so that purging works correctly
I am not that interest getting per-page cache clears, but having Purge button working in the site control panel would be nice and giving editors to easy to clear the cache in the case of emergency.
(Alternative I can show how to use varnishadm, but I think setting up Varnish and Plone to discuss each other cannot be that difficult)
What have you filled in the caching control panel?
One oddity is that you need to always add the port to the domain, so something like http://example.com:80 (the docs are fixed in SVN) if you want to accept multiple domains.
If you run Varnish on port 80, it should be clear that virtual host rewriting doesn't happen in front of Varnish, so you set the corresponding checkbox accordingly.
Related
I have installed GitLabv13 on ubuntu 20.04 using the standard procedure where external_url is set to a relative URL, i.e., http://www.example.com/gitlab.
I get a 404 when I navigate to the URL via the web browser.
I tried the basic troubleshooting found on GitLab's site, but that does fix the problem.
I am not running any firewall, and port 80 is not blocked.
What else should I try?
First, the CPU/Memory requirements for GitLab are more than 1 CPU/2GB.
Second, make sure all configuration files listed in "Install GitLab under a relative URL" are modified.
The troubleshooting page suggests checking the format in gitlab.rb.
And issue 244 suggests, for testing, to force the IP address in /etc/hosts.
My solution was to shutdown the existing Apache webserver running on the same machine, at which point, I no longer received a 404. However, due to the minimum requirements - I am only running a single core CPU with 2GB RAM - I now receive a 502.
I am new to Linux command line and setting up Magento 2.1 on my VPS. I am thinking to setup Nagios on subdomain so i don't want any interruption on my actual domain ecommerce application.
I have few doubts which causing lot of trouble to me.
By default Zpanel comes up with lower config for Php and Mysql and to make them work with Magento 2 i have to manually upgrade them . I did that but Magento worked, whole Zpanel navigation stopped working. So i re-installed whole ubuntu Os again and ready with my box. I would also like to have Varnish Cache along with some web based console so that i can easily manage my virtual hosts and for some other stuff.
What will be the best approach to setup everything one by one on one domain/sub-domain? I have found so many articles to install magento 2 on ubuntu using command line but they dont use any webpanel. I am open to switch it to any other OS as well.
If there is sequence to setup these all, please guide.
Final Requirement:
Magento 2 with any Linux OS
Nagios server for monitoring
Web panel like CWP or Zpanel etc.
This question will be complete solution and will helpful many other users as well. All answers are highly appreciated. Thank you all in advance.
Regards
H
Basically took a backup from server and restored it on my machine. Everything seems to be displaying correctly. But when I go to my System Settings, there are missing settings. But when I check modx_system_settings, they're there. Also cleared cache multiple times, so that's not the issue it seems.
Any ideas?
Thanks!
there is a cache_system_settings and cache_context_settings... though if you have cleared cache multiple times. actually delete the files to verify. Is it possible that you have context settings that would be overriding system settings? It would be helpful to tell us what settings are "missing"
Are you sure that the you crosschecked the same database tables? Is the table modx_system_settings the same table that MODX installation has in use?
Another possibility could be a not writable cache file in core/cache/system_settings or core/cache/context_settings.
Found the answer for my case. Basically it was server related. Live server is using linux, so when I set it up on my local which is wondows based, I had to search systems settings in DB for "locale" and update the value to English. That fixed my system settings. Everything showing now.
I decided to reinstall Sitecore 8 instance via wizard, I have removed instance and install a new one with the same name XYZ.
but after reinstall it I am getting an error in browser - ERR_NAME_NOT_RESOLVED
I checked IIS binding, I checked hosts file, reset DNS, restart PC and etc I still get this error in any browsers.
How I can fix it? What is the issue?
I have found solution https://support.microsoft.com/en-us/kb/2823477 but I can't understend how sitecore installer can change it.
Generally, the process of site resolution goes in the following consequence:
DNS - find ip address by the hostname (from request header)
Access IIS with that IP (and port if not default 80)
IIS checks bindings by hostname from header and serves corresponding website.
Website being resolved has (merged) web.config in root folder. It has node with all sites served by current Sitecore instance, being listed. Order does matter! First successful match (by hostname or port or default) works it out.
Site being found on previous step has startItem property which is your Sitecore item served by dafault.
Please go and carefully check all those steps to see where it breaks. Also I have previously write a blog post, you may find it helpful with more details on that:
http://blog.martinmiles.net/post/how-websites-are-resolved-with-sitecore
Do any sites work with a Local name configured in 'hosts'?
You may need to disable the Loopback Check in your tcpip stack. Windows uses this as a countermeasure for man in the middle attacks by default on many systems. A registry change is needed to allow a machine to refer to itself using a name that is not its own Hostname. Sorry, but I can't remember the actual key.
BACKGROUND
We are upgrading an umbraco 4.5.2 site running on Win2k8r2 / IIS7.5, SQL2k8r2 to umbraco 4.11.10. Given the number of steps required to perform the upgrade, we chose to do it offline and then replace production with the updated db and file system.
We did an offline upgrade to bring it up to 4.11.10 (4.5.2 -> 4.6.1 -> 4.7.2 -> 4.8.1 -> 4.9.1 -> 4.11.10). These upgrades affected the database and the filesystem.
The old system has 14 domains resolving to the 1 umbraco site. The domains are just aliases and per requirements are not set up with redirects from 13 of the domains to a master - instead, each domain serves the same content - just with a different host.
The 14 host headers are defined in IIS. They are also defined in umbraco under:
Content (folder)
EN (language folder)
Home (Hostnames are defined here)
Top Level 1 (also a child of EN)
Top Level 2 (also a child of EN)
PROBLEM
When we test under localhost (which is defined in IIS but not as a hostname in umbraco), the site renders content as expected. However, when we test with one of the hosts defined in IIS and in umbraco host names (after setting it up to resolve to 127.0.0.1 in hosts file), we are able to get to the home page but all other pages result in a 404.
The home page and preview pages render fine and the content editor and other backend admin features work fine. However, the "nice url" pages do not render and get 404 errors.
WHAT I'VE TRIED
I have deleted app_data\umbraco.config and republished the entire site.
Create a new website in IIS. Still get the 404 on pages other than site root.
Looked in umbracoLog table. Didn't see anything about 404s or anything that looked unusual in relation to before/after upgrade but I'm not an umbracoLog expert.
Is it necessary to do a clean install of 4.11.10 to install prerequisites that I may be missing? If so, what are these prerequisites and can they be installed independent of 4.11.10 install?
I'm at a loss as to what might be causing the issue. Any help would be appreciated.
A combination of items fixed the problem.
The main problem was having the hostnames defined in umbraco under the Home node. I removed the hostnames defined in umbraco at the Host node. Hostnames still exist in IIS.
In config\umbracoSettings.config
Set <useDomainPrefixes> to false
Set <addTrailingSlash> to false
In web.config set umbracoUseDirectoryUrls to true
Finally, fix a side-effect of removing the umbraco hostnames that causes requests for / to resolve to the EN node by adding the following to config\UrlRewriting.config
<add name="SiteRootHack"
virtualUrl="^~/$"
rewriteUrlParameter="ExcludeFromClientQueryString"
destinationUrl="~/home.aspx"
ignoreCase="true" />
There are several things you should check, but if you are getting Umbraco's 404 page and you can access the backoffice then that is a good sign at least!
The first thing to do is check Umbraco's logs at ~/app_data/logs/ to see what Umbraco is logging upon each request, if anything. Then check:
Have you installed MVC3 and 4 on the server?
Is the application running in a .Net 4 integrated app pool?
Have you applied "write" permissions to the correct folders?
Try removing any domain settings you have in the Umbraco backoffice, these are almost redundant if the site is a basic install.
If possible you should also create an Umbraco project from NuGet, this way everything you need with regards to DLLs dependencies are installed in the project. Also, there shouldn't be any need to upgrade in so many steps. It should be possible to upgrade from 4.5 to 4.7 then to 4.11 directly.
Finally, check the breaking changes in the Umbraco versions. For example, GetProperty("propertyName").Value returns a string in one version and then was changed to object in a latter version possibly 4.11, so this would obviously start causing NullReference exceptions which may be inadvertently be causing the 404's. It is unlikely you would be able to upgrade like this without having to make some code changes.