I'am getting Invalid base url
I'am getting Invalid base url after updating layout.
{"message":"Invalid base url"}-
Hi Mohamed,
this means that after the sync something has been changed on the server - it was added SSL certificate, or it was added a redirection option from non-www to www or any other actions with this folder.
The server sync "Golden Rule" is: Server Sync option is the last step in publishing a Brizy Cloud project. The entire server environment needs to be prepared before uploading the Brizy folder.
Now, once the SSL or redirect changes have already been made, you need to delete the project folder and re-upload it again.
1 -
Solved, Thanks a lot
0 -
I'm happy to help ;)
1 -
Would've been very helpful if this was included in Brizy Cloud instructions during publishing of a project for the first time. Spent a great deal of time trying to figure this out earlier. I hope this does the trick. In the process of wiping out root folder on one project to republish again.
1 -
Hi Marcelo,
will ask colleagues to add this note to the documentation.
0 -
hello i get {"message":"Invalid base url"} when www is used but whem http://happysbakery.co.uk works fine
but http://www.happysbakery.co.uk gives invalidbase url i have no SSL running
what procedure should i use
cheers kola
0 -
Hi Kola,
Can you confirm that you have added A Record?
0 -
hi sorry could you assist as i have access to add anything from my host and what do we need to do
0 -
here's an article on how to add an A record: https://www.name.com/support/articles/115004893508-Adding-an-A-record and you can find our IP address in the cloud dashboard: https://jumpshare.com/v/YmqG89L5LKxAAR8SEatw
0 -
thanks im hosting in my own server we planning to use ypur platform for all work so would be good to get this sorted with your help
0 -
I could send ftp amd also admit crendtials for your help
0 -
My Brizy site is displaying on http but not https.
I've followed the advice about and I've done all the server set-up with SSL certificate and mapped the directory files before loading the WebFTP files.
I've even deleted the files and re-uploaded. I've also deleted the entire site from my server and started anew about 3 times.
I've spent over an hour of time with my DreamHost support team trying to resolve the issue and the issue persists.
They even attempted to force the https with the following code with no success:
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NE]
I really want to get this issue resolved so that I can continued creating landing pages for myself. They think that there may be something in Brizy code that is causing the issue.
One thing I've noticed is that my the domain listed under my project in my Brizy dashboard is http:// instead of https://. This may not mean anything, but I need help with this. Please help.
0 -
Hi guys,
@Kola Moradeyo is your site published through Server Sync or Custom Domain?
@Steven Lozada, from what I know you've already had several discussions with my colleagues Natalia and Sandra. I'm afraid we can't help you. This is related to your hosting provider and we don't have time and resources to inspect this. The Server Sync just put the files on the server and do not influence the URL in any way. Everything related to the domains is related to the hosting provider.
If you can't solve this with guys from DreamHost, try publishing your site from scratch. Delete everything, make sure your domain has https, and then add the server sync folder there.
0 -
Hi,
I've had my hosting company (DreamHost) looking into this issue. They've spent a lot more time than the Brizy support team trying to locate the error mainly because I get 24/7 support from them.
They were the ones who gave me the rewrite code to correct the original error that I was getting with my Brizy not going to https. They're claiming that something is wrong with the log files that keep pointing to http, but that code forced it to https and it worked. I subsequently shared this info with Brizy.
Then Brizy changed the .htaccess code in the site files and the rewrite code my hosting company gave me stopped working. I worked again with DreamHost on Saturday for about 45 minutes to find and correct the error and after trying various tests and code changes they've instructed me to come back you because they think the error is coming from your coding somehow. I'm now stuck because both parties think the error is not on their end.
The other concern that I have is that the other Brizy sites that I loaded prior to Brizy changing the .htaccess code are working properly.
What do you suggest I do to attempt to correct this with DreamHost? What should I ask them to look for that could be causing this error?
0 -
Hi Steve,
I understand your situation but there are two moments that argue our position. Brizy does not change the .htaccess code in any way and Brizy works well on your other sites.
Have you tried deleting the var/cache file? There may be something to this. Also, please leave at least a link to your site. Maybe we can inspect something.
1 -
hello im using server sync code
0 -
HI @Kola Moradeyo,
In this case, the SSL issue relates to your server provider. Through Server Sync we just add our files and do not influence the url.
Please refer to my first response: https://support.brizy.io/hc/en-us/community/posts/360056759991/comments/360009209731
0 -
Hey, I got same error. I did what was suggested, deleted all files and downloaded all files again. i use server sync version. But still nothing. Can you check that please by our side?
Domain dinine.one is the address.
Thanks!0 -
Hi Piotr,
Have you tried deleting the var/cache file? There may be something to this.
0 -
Yes, I reached the hosting company. Nothing.
Also, I deleted all from server. Waited a few hours, nothing.
So I decided to download HTML self-hosted version, worked with no problems with SSL.
But I want to have version server sync, so few minutes I loaded back - still no SSL. The problem is on your side somehow.
Maybe you should add some tick to be clicked over the projects - like is it with or without SSL?
And still - I need your help with it.
Project ---> dinine.one.0 -
Hi Piotr,
I have created a ticket for you and we will try to help you.
0 -
Great!
0 -
So, I've been struggling with this INVALID BASE URL myself:
[Note: make sure you've got the basics covered, like having your SSL certificate active FIRST]
How To Make Sure Your Server-Sync Install Works For all cases (WWW, HTTP, HTTPS.)
Installing a "server sync" version of the site in the root directory of a folder on my server works in all cases EXCEPT when I use the www. subdomain.
I tried different CNAME and A Record configurations but that didn't work.
I tried the .htaccess snippet provided here (and lots of other places.) and that didn't work
Then I found a variation of the .htaccess snippet THAT DID WORK (edit your .htaccess file to include the following code) ... Here it is:
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteCond %{HTTP_HOST} ^(?:www\.)?(.+)$ [NC]
RewriteRule ^ https://%1%{REQUEST_URI} [L,NE,R=301]
Here was the article I found the solution in:
https://simonecarletti.com/blog/2016/08/redirect-domain-http-https-www-apache/It worked for me, I can sleep well tonight.
0 -
Hey,
thanks for sharing. You can create a new post with this and it will be more visible.
0 -
Hello, I have gone through this discussion many times tried hat has been said but my site is still giving me some this same error. Can you please assist with a solution. I need to use the server sync method . my site is https://creative21.co.zw/
And why does is create the cache folder automatically?
0 -
Hello!
This message -- {"message":"Invalid base url"} -- is related to SSL or www redirect settings. All these settings should be changed/edited before uploading the Brizy project in your server/folder. What you should do now:
1. Delete Brizy folder from your server/folder
2. Download again Brizy zip folder.
3. Unzip the Brizy folder
4. In the htaccess file, remove "#" for both redirect rules, video - https://bit.ly/347UCBR
5. Save this file and upload all other files and folders in your server.
Everything should work in a couple of minutes.
Regards, Natalia
-1 -
Hi my code looks like thison ht access files can you give me the correct one that i can just paste in and save
RewriteEngine on
RewriteCond %{HTTPS} off
RewriteCond %{HTTP:X-Forwarded-SSL} !on
RewriteCond %{HTTP_HOST} ^creative21\.co\.zw$ [OR]
RewriteCond %{HTTP_HOST} ^www\.creative21\.co\.zw$
RewriteRule ^/?$ "https\:\/\/creative21\.co\.zw\/" [R=301,L]
-1 -
Hello!
This is the correct code:
RewriteEngine on
# --- Redirect from http to https
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
# ---
# --- Redirect from non-www to www
RewriteCond %{HTTP_HOST} ^creative.co.zv [NC]
RewriteRule ^(.*)$ https://www.creative.co.zv/$1 [L,R=301]
# ---
-1 -
I think we've come up with the complete solution for everyone. Took us about 4 hours of trial and error, but this seems to be the correct combination:
# 301 REDIRECT HTTP TO HTTPS AND WWW TO NON-WWW
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteCond %{HTTP_HOST} ^(?:www\.)?(.+)$ [NC]
RewriteRule ^ https://%1%{REQUEST_URI} [L,NE,R=301]RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond $0#%{REQUEST_URI} ([^#]*)#(.*)\1$
RewriteRule ^.*$ %2index.php?page=$0&%{QUERY_STRING} [QSA,L]
</IfModule>See if that fixes everyone's issues.
I noticed that the original htaccess file is trying to force non-www to www but that doesn't work. From everyone's sites I looked at above, everyones sites worked with https, but not www. We ended up then doing a domain level redirect of www to just the domain and that solved the issue if someone typed www.domain. It redirected to just domain.com. But then, if someone did https://www we then got a ip not found
So then, after hunting and hunting again, we found the http to https and www to non www as you see above and then re added their original rewritebase. After diving into that that file does, I saw that it checks to see that the particular file you are looking for is located in the directory/file mentioned. because it was www and it is looking at non www, with no way of forcing the www, I'm assuming that was the culprit.
I have not tried to update anything in brizy to see if it syncs yet BUT.... now it works with https://www, https://, www, and just domain.com. They all are directing to https://domain.com
Let me know if that works for people.2 -
Works great, thank you very much David.
This problem was driving me crazy.
Regards,
Barry.
0
Please sign in to leave a comment.
Comments
31 comments