https access
By webjo on Thursday, 09 July 2015
Posted in Technical Issues
Replies 15
Likes 0
Views 0.9K
Votes 0
As a matter of practice, I access the administrator panel of my Joomla sites via the secure link provided by my hosting provider. For example, if my site is located at

http://xxx.yyyyyyy.com/~preview/sitename/

I would access the Joomla admin at

https://xxx.yyyyyyy.com/~preview/sitename/administrator/index.php (note the https)

After upgrading from EB 3.9 to 5.0.14, I can still access the EB admin, but nothing saves to the database. For example:

- I can't save edits to existing blogs or create/save new blogs (no saved message displays)
- Checking for Updates feature icon on the Dashboard hangs (does not show current version)
- The Database sync doesn't run

In addition, I get the following error on the admin page (Dashboard) in the browser debugger:

POST https:///xxx.yyyyyyy.com/~preview/sitename/administrator/?option=com_easyblog&_ts=1436456389427 404 (Not Found)

n.ajaxTransport.send @ admin-5.0.14.static.min.js:150
n.extend.ajax.v.send @ admin-5.0.14.static.min.js:144
(anonymous function) @ admin-5.0.14.static.min.js:288
(anonymous function) @ admin-5.0.14.static.min.js:269

If I access the admin using an unsecure link (which I was able to do with EB 3.9 and need to be able to do again) the EB Dashbloard works and I am able to save and edit posts.

What do I have to do to be able to access the EB admin using the secure link for the Joomla admin that I've always used?

Thank you.
Hi webjo,

Sorry for late reply to this,

Perhaps you can provide us with your Joomla backend and FTP access so we can better have a look of this issues?

*You can put the information in the optional information field below(SITE DETAILS). Don't worry about privacy. Only Support team can view the information.
Arlex Wong
·
Friday, 10 July 2015 10:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Details provided.

Notice that the EB 5 admin only works on a temporary server if I've created a subdomain for the site. The subdomain URL is not secure. I need to be able to access the site and have the EB 5 admin work using the secure temporary URL with https in order to test installations on my test server before doing it on a live server. That's pretty standard practice.
webjo
·
Friday, 10 July 2015 22:31
·
0 Likes
·
0 Votes
·
0 Comments
·
Do you already have your desired domain pointing to your server or have a SSL cert installed? If there's at least a cert installed I personally prefer modifying my local host file to point the domain to the server's IP to avoid temp URLs. I tend to get nothing but problems with temp URLs and prefer making my website on the domain itself even if the domain isn't publicly active yet. If a. SSL cert isn't installed yet you could always acquire a free one for testing purposes. Depending on your host, they could also generate a self-signed cert for testing as well.

I realize my reply doesn't directly fix your specified problem but again I prefer to avoid temp URLs entirely.
David Montoya
·
Saturday, 11 July 2015 00:33
·
0 Likes
·
0 Votes
·
0 Comments
·
Also, if you're just accessing your host's SSL portal for sake of development security, then I recommend either developing on a local server or using an IP whitelist. Simplifies the problem greatly.
David Montoya
·
Saturday, 11 July 2015 00:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks David for the comments. Maybe I should not have stressed the development vs. live use of the secure links. Even on all of my production sites I always access the admin from the secure link my host provides, and I ask any of my clients that use the back-end to do the same.

The point is that if every other extension is able to work on this secure URL (including Easy Blog until version 5) then there must be a bug that's preventing it from working now.
webjo
·
Saturday, 11 July 2015 07:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Oh I completely understand. I've avoided temp URLs like the plague because it tends to break things for me. In example, attempting to use it on my site completely 404s it. By the way, do you already have Joomla's backend set to force the use of HTTPS? I'm curious if that'd affect it. However if your site doesn't have SSL installed it'll cause other problems...
David Montoya
·
Saturday, 11 July 2015 07:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi webjo,

I'm really sorry that delayed of this reply,

I've checked in your site, it seems like the reason why you hitting this issues (- I can't save edits to existing blogs or create/save new blogs (no saved message displays)) is because the Easyblog ajax call http://yoursitedomain.com/index.php?option=com_easyblog rather than http://yoursitedomain.com/?option=com_easyblog

To replicate this you can access
https://yoursitedomain.com/administrator/?option=com_easyblog&_ts=1436773283376 (this show out 404 error)


404 Not Found

The server can not find the requested page:



xxxx/administrator/ (port 443)

Please forward this error screen to xxxx WebMaster.


And
https://yoursitedomain.com/administrator/index.php?option=com_easyblog&_ts=1436773283376 (this can be access)

it seems like your server restrict to use index.php , so made the Easyblog script broken, can you provide us with your FTP access so we can test around and see is it got better solution for this?
Arlex Wong
·
Monday, 13 July 2015 16:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Please see private question.
webjo
·
Tuesday, 14 July 2015 04:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi webjo,

I'm really sorry that delayed of this reply,

Yes, I have installed OSE extension in your site for troubleshoot on this issues, but I didn't touch any RokSprocket module from your site.

May i know do you have do the backup on your site? keep us updated then.
Arlex Wong
·
Tuesday, 14 July 2015 17:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for letting me know. Although I'm surprised and disappointed that you would install an extension on a customer's site as part of the troubleshooting process. I don't know what has caused my RokSprocket content to be deleted (not the modules just the content is gone). This was a cloned site on a test server, so I'm lucky that I don't have to worry about backup.

Have you made any headway on the https issue? Although I cannot provide FTP access I am more than willing to either participate in a screen sharing session or take direction as to what files to edit.

Thank you.
webjo
·
Wednesday, 15 July 2015 09:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi webjo,

I'm really sorry that delayed of this reply and apologize that I should consult with you can I have the permission install file manager in your test site before I do troubleshoot, because without debug from your file directory that is hard for me to see what is issues causing this issues. hope you understand

Can you try download my attachment file and replace in JoomlaFolder\administrator\components\com_easyblog\includes\configuration\configuration.php and see how it goes?

if this file doesn't help, may i know do you know your server is it force to use `index.php` for access all the page from backend?
Example :
https://your.sitedomainName.com/~preview/twd2015/administrator/ (hitting 403 forbidden)
https://your.sitedomainName.com/~preview/twd2015/administrator/index.php (can access directly)

Keep us updated the result.
Arlex Wong
·
Wednesday, 15 July 2015 12:03
·
0 Likes
·
0 Votes
·
0 Comments
·
Uploading the file did not fix the issue unfortunately. Even if the server is forcing the use of 'index.php' in the URL, the workaround has to come from a change with EasyBlog.

I am accessing the site's admin the same as I always have and EasyBlog worked fine this way before the upgrade to EB5.

The contents of the site's htaccess file is included in the Optional Information below if that will shed some light on a solution.

Thanks.
webjo
·
Thursday, 16 July 2015 12:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey there,

This is actually not an error with EasyBlog and it has nothing to do with your htaccess either. You need to consult this with your web hosting provider to ensure that the site is accessible via https://site.com/~preview/twd2015/administrator/?option=com_easyblog

EasyBlog's ajax calls are made to the server without index.php because there are a lot of sites out there which redirects http://site.com/index.php to http://site.com . If we made an ajax call to http://site.com/index.php , it would fail for them since they are performing redirection.
Mark
·
Thursday, 16 July 2015 13:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Before I bring this to my host, please explain why this has always worked with prior versions of EasyBlog. I am currently administering EasyBlog 3.9.24862 on more than one site and I have no problems.

Are the ajax calls you're referring to a new feature in EasyBlog 5?

I'm afraid if this can't be solved I will have to use v3.9x until you don't support it anymore and then move to a different extension.

Thanks.
webjo
·
Thursday, 16 July 2015 13:59
·
0 Likes
·
0 Votes
·
0 Comments
·
It's a chicken and egg situation here because in EasyBlog 3.9, the ajax calls were made to the /index.php but we have received a lot of error reports from customers because they have a redirection going on from http://site.com/index.php to http://site.com . Hence, we decided to switch to http://site.com/ . If we are going to use /index.php again, then these other customers would face similar issues as you.
Mark
·
Thursday, 16 July 2015 16:37
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post