I've recently installed Magento 1.9.4.3 on my cPanel. Setup was successful without any error but now I'm unable to login to the admin panel.
Please guide me what should I do.
Did you install a clean version by installer or an upgrade to an existing version?
On new installations it could be an Cookie issue (base un/secure URL) not set as well as cookie domain in database, which causes the admin panel to just reload.
If you updated an existing version, try to delete your cookies and cache. Sometimes, after installing (or changing, session save type, module installation etc) the admin panel is just reloading. Deleting the cookies and forcing a reload on the page, fixes it most times. If not, just send a message for more instructions
Related
I have the following problem and now after several days still can not solve it.
I am upgrading an Electron app from version 12 to version 22. The app is there to make certain data packages of our customer more manageable. I have already managed to update the app to version 22, but there is still an error that occurred when updating from version 14 to version 15.
To log in to the app, the external login page of our customer opens in a second window of the app. The login is handled there. I only get back whether the login was successful or not. Afterwards it is checked if the file packages are up to date or if updates are available ect.
So far, everything works fine. But from version 14 to version 15 of Electron there is a problem. The login works, but the following query for updates ect. fails. This query is only possible if you are logged in.
In the Developer Tools I see that I get redirected from request url to the login page. As far as I understand, the Problem is related to the cookies. As if the query would not have access to the cookies of the successful login. But when I look at the breaking changes of version 15 I don't find anything about it.
Does anyone know what the problem could be or how I could fix it?
I have a Vue app that is used both in the browser and as a PWA. I would like to ensure users receive the latest version whenever updates have been pushed to the server.
I am using Nginx, Django and vue-cli along with #vue/cli-plugin-pwa.
Currently when I npm run build and then push the new version to the server, users get the old version of the app (in browser as well as PWA on their phones). To get the new version they do a hard refresh in the browser or for the PWA they close the app and reopen it again.
Is there a way to ensure a version check is done every time the app is loaded so that the new version is retrieved?
In the end I found this excellent article which covers how to display a notification when an update is available. The user is then able to click the notification which updates the app.
https://dev.to/drbragg/handling-service-worker-updates-in-your-vue-pwa-1pip
I'm having the strangest problem with Jira.
We were in the process of setting up links between Jira and Confluence and everything seemed to be working. After a restart of the machine we had some startup issues due to disabled plugs. We resolved this by deleting the rows indicating inactive plugins in the MySql database.
Everything seemed to be working. Could log into Jira. Could log into Confluence. Could connect from each to the other using application linker widget in the upper left corner of the applications.
While trying to embed some Jira into a Confluence page a user got an error and we checked the Application links.
Application link from Jira to Confluence looks good.
Application link from Confluence to Jira looks like this.
If I log onto the host machine and try to log into Jira as http://localhost:8080 i get this very strange behavior:
http://localhost:8080 brings up my Jira log on page.
If I try to log on as userX I get a try again screen.
If I try to log on as userY I get a try again screen WITH A CAPCHA.
BOTH logons DO WORK if I try to logon from https://jira.myorg.com!!!
Really confused why I can access the application but authentication fails. Any help would be greatly appreciated.
I'm still seeing this strange behavior but I've solved the problem by changing the application url to the outward facing one (https://jira.myorg.com). At one point this didn't work (that's why we used http://localhost:8080 in the first place, jira and confluence are on the same server). It seems to not need this at this point.
We did delete and recreate the links from scratch also. This is mention as a suggestion in the documentation if you are having problems with the links.
I'm weblogic newbie, trying to abandon it ASAP, but that's not possible for now, so I have to resolve this. Maybe following is completely normal and trivial. I don't know. Please advice.
I had working weblogic 12.1.3 on 2 PCs for months. But suddenly, I cannot log into admin console on neither of them. I enter username/pass from password store, and it's not accepted. While at the same time intellij idea successfully logs in and deploys app using same pass. OK, fair enough, we reset pass, using:
https://oracle-base.com/articles/11g/reset-the-adminserver-password-in-weblogic-11g-and-12c
and update password in intellij settings. Good. Intellij idea is in again, I cannot login. Nothing in logs, neither application, nor server logs.
I cannot login regardless if I start weblogic via intellij run configuration of from bash.
OK, lets try reinstall weblogic. No change.
Weblogic is up and running, app deployed to it, and is responsive. When accessing console URL, it gets printed, that app is being deployed, but I still cannot access it. Cleared caches/cooking etc. nothing. No logs, no error response. Nothing.
Responses to "failed"(?) login on urls j_security_check, console and console/ are http status 302 (moved temporarily). Not sure if it's ok or not, well say I'd expect 401/403, but maybe 302 is valid weblogic response for denied authentication. I don't know.
Any idea?
What you can do is to check web storage and try to clear it. But the most clear way is to use different browser. Or use your current browser in private mode. Also in firefox you can create different profile and use it for this specific purposo.
After upgrading server to Debian Wheezy I get a strange problem: after login via basic auth (which works), trac opens, but looks like I not logged in into it, like anonymous. And I cannot create task, comment and so on.
After upgrade system I reinstall trac via standart python ./setup.py install, and nothing else.
How to fix this?
I dont't know what the cause of the problem, but after recreation new working dir, reconfiguring apache to this new dir, all works fine.