• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • 😌 This community is user driven. Be polite with other users.
    • 👉 Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • 💸 Purchase a Pro Subscription to get access to active software support and faster ticket response times.
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Alibaba Cloud OSS 500 error

Cee

Cee

Chevereto Member
▶🚶‍Reproduction steps
  1. I tried to use Alibaba Cloud OSS. The information I filled in was correct, but it returned a 500 error. What should I do? Is it Chevereto's problem?
😢Unexpected result

QQ截图20200114225326.png

📃Error log message
QQ截图20200114225116.png
POST https://img.tg/json 500
Uncaught TypeError: Cannot read property 'error' of undefined
at Object.error (chevereto.min.js?0e0058f0cc676fa6f938be652187b1a3:262)
at Object.<anonymous> (peafowl.min.js?0e0058f0cc676fa6f938be652187b1a3:192)
at c (scripts.min.js?0e0058f0cc676fa6f938be652187b1a3:1)
at Object.fireWith (scripts.min.js?0e0058f0cc676fa6f938be652187b1a3:1)
at k (scripts.min.js?0e0058f0cc676fa6f938be652187b1a3:1)
at XMLHttpRequest.r (scripts.min.js?0e0058f0cc676fa6f938be652187b1a3:1)
 
Sort by date Sort by votes
When I re-added the repository, he successfully saved it, but the existing repository 2 could not be changed. Also do they not support deletion?
QQ截图20200114230606.png
 
Upvote 0 Downvote
You need to actually click the response where it reads > POST http://..../json 500

Then and paste the raw response that will appear in the "Response" tab.
 
Upvote 0 Downvote
Please acknowledge that the error display may be hidden. You need to enable display errors or simply fecth those at the error log file used by your web server.
 
Upvote 0 Downvote
You are showing me console errors, not php errors. I need the error reported to the backend, not the front. Enable display errors and the error will be shown in the /json response tab. Alternatively, the error should be being logged at your server error log file.

Both alternatives are suitable to get the error reported at the backend.
 
Upvote 0 Downvote
Rodolfo said:
You are showing me console errors, not php errors. I need the error reported to the backend, not the front. Enable display errors and the error will be shown in the /json response tab. Alternatively, the error should be being logged at your server error log file.

Both alternatives are suitable to get the error reported at the backend.
Click to expand...
1579037496826.png
 
Upvote 0 Downvote
Correct, that's the error log file needed.

However, I'm seeing issues affecting local storage, not Alibaba. Kindly attach the whole document or the entries related to alibaba to be able to narrow it down to the issue being reported.
 
Upvote 0 Downvote
What I can understand from the logs is that there's a conflict with the endpoint, the issue is thrown directly by the Alibaba API server. On my end I'm able to use Alibaba OSS on the demo, but I was unable to test the same region you are using:

In compliance with the Peoples Republic of China (PRC) laws, purchasers of Internet related products offered in a region inside Mainland China are required to provide real-name registration information.
Click to expand...

For reference, the demo has he following settings:
Code: 
Region: oss-us-east-1
Endpoint: oss-us-east-1.aliyuncs.com
URL: https://chv-demo.oss-us-east-1.aliyuncs.com/
Bucket: chv-demo

I was able to trigger the issue by using the region oss-cn-shenzhen.aliyuncs.com in the Chevereto External storage:

1579114475952.png

In this case, the error is triggered because I used a different region, which is not supported by the Alibaba OSS API. The only valid endpoint for the chv_demo bucket is oss-us-east-1.aliyuncs.com as shown in the bucket overview:

1579114555611.png

Just make sure to use the right endpoint and it should work.
 
Last edited:
Upvote 0 Downvote
Rodolfo said:
What I can understand from the logs is that there's a conflict with the endpoint, the issue is thrown directly by the Alibaba API server. On my end I'm able to use Alibaba OSS on the demo, but I was unable to test the same region you are using:



For reference, the demo has he following settings:
Code: 
Region: oss-us-east-1
Endpoint: oss-us-east-1.aliyuncs.com
URL: https://chv-demo.oss-us-east-1.aliyuncs.com/
Bucket: chv-demo

I was able to trigger the issue by using the region oss-cn-shenzhen.aliyuncs.com in the Chevereto External storage:

View attachment 2747

In this case, the error is triggered because I used a different region, which is not supported by the Alibaba OSS API. The only valid endpoint for the chv_demo bucket is oss-us-east-1.aliyuncs.com as shown in the bucket overview:

View attachment 2748

Just make sure to use the right endpoint and it should work.
Click to expand...
I guarantee that the endpoint and the area I choose are exactly the same. For the same OSS connection information, I can add an OSS option to the external storage, but I cannot use the option that currently has problems. The information filled in is exactly the same, so it is not what you said The problem.
 
Upvote 0 Downvote
Unfortunately there's no that much I can do here. The response about the wrong endpoint comes directly from the Ali server and I don't have any way to test the alleged endpoint as I have a region lock.

I managed to replicate the issue, that's all what I reported here.

I guess that the issue needs to be debugged directly in your server, for that matter I will require server access, admin access to your installation and the credentials for the external storage.
 
Upvote 0 Downvote
1579138003647.png
1579138092451.png

As you can see, the information I filled in is exactly the same as the OSS information in the correct use, but it returns an error. The storage ID of 500 errors is 2. Because I cannot modify this error message, I added the storage ID as 3 OSS, but the information used is exactly the same. And he can work normally.

How can I delete this incorrect storage ID? I can confirm that this is an error caused by Chevereto.
 
Upvote 0 Downvote
And I hope to add the ability to manually delete external repositories, because there are many unused external storages that do not need to remain.
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top