I want to install a Joomla extension but I keep get an error:
Sorry {ip}, your request cannot be proceeded.
For security reason, it was blocked and logged.
If you think that was a mistake, please contact the webmaster and enclose the following incident ID:
[ #4677055 ]
I am logged in as superuser. I tried to clear the cache but still no change.
After some investigation I found that this is a problem generated by "ninja", which is a firewall or something.
Sounds like you have a Firewall extension installed that blocks the install action. This could either be NinjaFirewall or AdminTools. Please check for these and others, and remove the block in its configuration. They are most likely under Components or Plugins.
Related
I have 2sxc installed on a site. It was previously registered with the Patrons tokens for Core+, Patron Basic, and Patron Perfectionist.
I patched from 13.10.1 to 14.1.0. Now I get this error on all of my apps:
Warning: Registration is Invalid. Some features may be disabled because of this. Please reactivate the registration in Apps Management.
Under System, even though I tried re-registering my app by deleting the old one and starting a new one, I still see "Registered to: (unregistered)"
I went to reactivate my license but it doesn't make a difference. When I go to Extensions/Features, it shows as "Core (free for everyone)" 4/4 but nothing else.
I tried clicking "Retrieve license" but that doesn't seem to make a difference.
How can I register my app to get rid of this error message?
Sorry for the still clumsy process. We'll try to optimize ASAP.
The warning appeared because a major upgrade changes the fingerprint, so the previous activation is invalid. You will need to register the new fingerprint for things to work again.
On features-tab, just click on register and go through the normal steps to activate that fingerprint.
I have cloned the click-to-call repository and followed the steps as mentioned. I am able to login with said created user but then get stuck at /rtc API.I got some error in network panel. and "General SSL engine problem in console which is not correct. SSL certificates are all correct." Let me know where i went wrong. Please check the screenshot below :
I have had a talk with nexmo team, they said it is the ssl issue.
https://help.nexmo.com/hc/en-us/articles/207051767-Certificate-for-nexmo-com
Now I am unable to find where to import the certificate to my app?
I am the JavaScript Developer Advocate at Vonage (Nexmo).
You also filed an issue at https://github.com/nexmo-community/client-sdk-click-to-call correct? Thanks for that. I will also post my response here.
From your issue, it looks as if the Conversation Id is not being sent.
We recently merged some changes to the repo.
In your .env file, do you have SUPPORT_PHONE_NUMBER? That should be NEXMO_NUMBER.
Also, when calling the server, previously the code in the client.js around line 34 was application.callServer(); it is now application.callServer(application.me.name);
Let me know if this works for you.
Check with Nexmo - either you are out of balance or your account has been been marked inactive for some reason. Most of the time its because of insufficient balance.
I'm using Jenkins 1.651 with the IRC Plugin 2.27 and
instant-messaging plugin 1.35.
I've noticed that the IRC plugin logs a lot of INFO level messages to the Jenkins log (GUI and on-disk). I'd like to configure logging for this plugin, or disable logging for the plugin entirely.
I've tried adding a new log recorder for the logger hudson.plugins.ircbot, but the plugin still logged to the general Jenkins log. Any pointers?
I found this tweet:
https://twitter.com/russss/status/806560486166822915
(You can fix by changing the level of org.pircbotx.InputParser to WARNING at /log/levels in the web interface. Thanks, pircbot...)
I can confirm this works, but the config doesn't seem to stick after you restart Jenkins. If anyone knows where to capture this to make it permanent, that would be great!
Edit: so not ideal, in so far as it knocks all Jenkins logging back to the level of WARNING or higher (no more INFO messages) but this is a permanent fix to the problem you can capture in code and config:
Add the following to JAVA_ARGS for Jenkins (we typically do this in /etc/default/jenkins) :
-Djava.util.logging.config.file=/var/lib/jenkins/logging.properties
Then create the file /var/lib/jenkins/logging.properties, containing the following:
handlers = java.util.logging.FileHandler, java.util.logging.ConsoleHandler
.level= WARNING
No more IRC messages in the Jenkins log!
This answer actually provided by my colleague, mig5
There is a bug https://issues.jenkins-ci.org/browse/JENKINS-46099 that asks for addressing this issue in a persistent way.
I am finalizing my Joomla-site with a Siteground host and encounter the following problem: my site shows the IP-adress instead of the url. Although I type in the url (www.nooitmeerfile.be by the way), it shows the IP-adress.
Could someone please give me a step-by-step explanation on how to fix this? I happen to find a lot of fragmented answers cluttered around the web. I am a novice user, and I'm stuck :-)
Thanks!
Possible steps to debug your issue:
Check configuration.php public $live_site = ''; and try to add your
domain (without trailing slash).
Check if .htaccess file is not altered and try to download and use a fresh copy.
Check if you are using 3rd party sef components / plugins and try to disable them.
Clear your joomla and browser cache.
Contact your hosting provider if something in your hosting is misconfigured.
Hope this helps
So I've installed an extension in my Magento Enterprise.
I've been able to configure new options in the admin interface after installing the module.
However in the frontend it complains "table not found". Checking the database that is indeed true. Seems the mysql4-*.php scripts have not been run or failed.
Is there a log or something I can look at to see what goes wrong? From what I've read (difficult to find documentation on this) the modules db should've been initialized on the first request after it was installed and activated.
Any other suggestions to what I can check to find out why it's not initialized properly?
First step is to check the core_resource table. If there's a row for your module, then zap it. This will retrigger the setup resource process.