Akeneo import returning 500 on upload - akeneo

When creating a import-profile in Akeneo i.e. XLSX, and then trying to upload and import a file Akeneo shows the spinner for infinite time. When I use the inspector window i see that the POST request to /launch that is apparently part of the rest API ( baseURL /job-instance/rest/import/product_variant_import/launch ) is returning this 500 error preventing Akeneo from proceeding.
First i thought it might had something to do with upload permissions but uploading media works fine. Unfortunately because of the 500 error there is nothing in the apache logs.
I'm using the basic apache configuration that is suggested in the set-up guide ( https://docs.akeneo.com/3.1/install_pim/manual/system_requirements/manual_system_installation_debian9.html ) under Apache.
I can't find anything on this subject online (Akeneo import + 500 error), so hopefully any of you have suggestions on what might cause this.
Best,
Seb

You should check the log and to have more information. And know what is happening exactly. If you can't check it, try to use xdebug to debug akeneo and stop it here:
/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php
Line 225:
private function handleException(\Exception $e, $request, $type)
And you will know what error you have.
EDIT:
We were talking via slack, and he sent me the error. He had problems due permissions
The error that he sent me:
“Impossible to create the root directory “/tmp/pim/file_storage/13_Product_variant_import_CSV”.

Related

Google App Engine login fails with error 500

I have an appengine (Java) app with the ability to sign in via Google. For this I use
UserServiceFactory.getUserService().createLoginURL(...).
This has been working fine so far, and still works well locally (using mvn appengine:run) but on production it consistently throws a generic 500 while on /_ah/conflogin?state=~AJKiYcHHHXI45-... (the 5th URL of the login process, while already being logged in with Google) and I can find nothing relevant in the Logs Explorer at https://console.cloud.google.com/logs/...
I've since even updated to the latest https://mvnrepository.com/artifact/com.google.appengine/appengine-api-1.0-sdk/2.0.10 but the problem remains.
Where should I look at to solve this issue?
To find the root cause of this issue, you can find the logs for this error will be helpful.
In this documentation there is a sample query that you could try to check for logs error with status 500.
resource.type="gae_app" AND
log_id("appengine.googleapis.com/request_log") AND
httpRequest.status>=500
Alternatively you could also try running ‘gcloud app logs read’ as mentioned in this document to see if you get any logs.
The issue tracker mentioned by Rez in comment is marked as Fixed and after checking your issue I think it also relates to the same issue tracker. As it closed I suggest to get your issue resolved I recommend to raise new issue tracker by referencing the fixed one or else you may raise support ticket with google

E/Volley: [839] BasicNetwork.performRequest: Unexpected response code 404 for

I bought an app template to mess around with, and when I'm trying to login in this case via Facebook it's calling the API I set up according to the guide.
It's calling
http://IP/mobileapp_api/api/registerUser
Now it's giving me the 404 error because the API folder does not exist, but when looking through the documentation and double-checking everything I also notice that he also doesn't have an API folder, but he's able to get a response just fine.
How is this possible?
Link for the video documentation https://www.youtube.com/watch?v=G1OTEbnD6CM&t=324s
I've tried to reach out to the developer, but with the current covid situation in his home country, I doubt I'll get a reply anytime soon, hence why I've come here.
Not sure why, but uploading the files via CPanel and not Filezilla somehow made it all work.

Trying to implement in-app voice call from browser

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.

App Engine logs showing HTTP 301 for nonexistent URLs

I am running a website on Google App Engine. From time to time I get out-of-control bots or perhaps brute force hacking attempts that I see in my logs. Recently I've had a bot (I presume) trying to access administrator/index.php several times a second. That file doesn't exist on my site. If I try to access it, I get the standard 404 and this in my logs:
But for the bot I am seeing HTTP 301 in the logs and I'm wondering why. Does Google interpret the requests as a denial of service or other attack and automatically intervene? I haven't seen documentation stating as much, but I'm not sure why else I would be seeing the 301 instead of 404 for the same URL:
Does anyone have an explanation for this?
The log entires shown on the screenshots can be clicked & expanded to view additional information. As mentioned in the comment above two things could be checked there for further analysis of what's going on:
check the hostname of where the request came to & see if it's not the expected behaviour for that hostname.
if the json object is shown, navigate to protoPayload -> line -> [0] -> logMessage where something like redirecting "http://example.com/" to "https://www.example.com/" should be shown which could also clear things up a bit.

Problems using Twitter4j on GAE throws 401 just after deploy

Well, I'm having a weird error here:
I'm developing one GAE app to read some Twitter Data, and after read a lot of docs, I have it working on my test server (Running on my pc) but after deploy and test on the real (my appspot domain) it shows this message:
401:Authentication credentials (https://dev.twitter.com/pages/auth) were missing or >incorrect. Ensure that you have set valid consumer key/secret, access token/secret, and the >system clock is in sync.
message - Could not authenticate you
code - 32
I've tried to recreate my OAuthAppToken and OAuthAppTokenSecret keys, even changing the permissions to "Write, Read and Direct Messages" and even assingning one Callback URL but nothing seems to work...
I've tried using twitter4j.properties OR using setOAuthConsumer(TW_CONSUMER_KEY, TW_CONSUMER_SECRET) OR a ConfigurationBuilder whith the correct constants and I'm experimenting the same Issue.
I'm working with AppEngine 1.8.3 and Twitter4j 3.0.4
Iv'e been writing on log and the Twitter object seems to be well created... I dont understand why is working on my PC but not on the real app.
On some other post someone says that could be because it needs to use Sync clock.. but he doesn't explains where to change that property...
Did someone had a clue?
Ok, the problem was me (and Twitter.... well..... I really think it was Twitter problem for being so dark on his api messages)...
On testing server I was looking for an existing account and on the cloud I was looking for an inexistent one. So, It was my mistake. But seriously, what about Twitter saying: "Access Forbidden"? That doesn't have any sense...

Resources