C4illin / ConvertX

💾 Self-hosted online file converter. Supports 1000+ formats
GNU Affero General Public License v3.0
403 stars 9 forks source link

"Job not found" message when attempting to convert files #23

Closed bradkeller closed 3 months ago

bradkeller commented 3 months ago

I receive the following error when trying to convert files using the v0.1.1 release of your application:

{
    "message": "Job not found."
}

Configuration is as follows:

services:
  convertx: 
    image: ghcr.io/c4illin/convertx
    ports:
      - "3002:3000"
    environment: # Defaults are listed below. All are optional.
      - ACCOUNT_REGISTRATION=false # true or false, doesn't matter for the first account (e.g. keep this to false if you only want one account)
      - JWT_SECRET=aLongAndSecretStringUsedToSignTheJSONWebToken1234 # will use randomUUID() by default
      - HTTP_ALLOWED=true # setting this to true is unsafe, only set this to true locally
    volumes:
      - /home/brakelle/config/convertx:/app/data
aaron13223 commented 3 months ago

Just wanted to upvote as I got the same error.

Chesherr commented 3 months ago

I just wanted to add that I also have this issue. It seems like what is happening is it is adding extra text to the url that it forwards to for the completed job. For example https://convertx.example.xyz/results/,%203022 is what we get for Job 2 Results, but it should actually be https://convertx.example.xyz/results/2

Essentially it is appending ,%20302 to the beginning of the result number in the jub url. I will sift through the code that is responsible for this and see if I can add more info in regards to this.

I feel this could also be related to the reverse proxy as I have not attempted this from the local ip url

Chesherr commented 3 months ago

Im thinking it has something to do with formatting of this line. I could totally be wrong

https://github.com/Chesherr/ConvertX-Chesherr/blob/249bccdc7df32f4e04293f563e314f82067122c3/src/index.tsx#L680

C4illin commented 3 months ago

Sorry for the slow respond, @Chesherr found the correct line will fix this asap. Thanks!