-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected toke u in JSON at position 0 #13
Comments
Yep, I have the same! |
Well, its working in the cloud... try playing with the jwt secret ...
…On Tue, Jan 28, 2020, 18:24 kastov ***@***.***> wrote:
Yep, I have the same!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#13?email_source=notifications&email_token=AFTF65TQLIFQKXYZNQXC2C3RABL5BA5CNFSM4KLYKHRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKD66JQ#issuecomment-579333926>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65SXDK7EZKQA6GQVO5TRABL5BANCNFSM4KLYKHRA>
.
|
I tried, the same error. |
Oh, I am terribly sorry!
I need to update the article.
There is a slightly different way of configuring it now.
Please follow the instructions in this link:
https://www.ahem.email/blog/post/how-to-set-up-your-own-disposable-email-server
It is very similar, but the part about the properies.json is different.
I switched to a system that works with rmv variables to better support
docker deployment.
…On Sun, Jan 26, 2020, 20:06 Avinash Seth ***@***.***> wrote:
Hi
I followed this article
<https://www.freecodecamp.org/news/how-to-setup-your-own-disposable-email-server-b4cfd297afa7/>
and followed step by step process but still getting this error in the end
[image: image]
<https://user-images.githubusercontent.com/4149253/73139470-4d091600-4094-11ea-9de3-0b89abdc47fa.png>
node version v11.5.0
npm version 6.7.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#13?email_source=notifications&email_token=AFTF65VAVAYXOEPFFAU67H3Q7XGJXA5CNFSM4KLYKHRKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IIYVPBA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65SARTKSM3FLMU4DAU3Q7XGJXANCNFSM4KLYKHRA>
.
|
Hi, I'm getting the same error and the link you reference is not available. Any other tips you can offer? I'm actually using Docker and it looks like ahem.js reads environment variables, is that right. Will using env variables solve the problem? I'd rather use a json file anyway so please let us know the correct way to configure. Thanks! |
The cloud is gone, the domain exlired today abd I an not renewing it.
I don't know what to make of the issue.
Can you send me the token?
…On Fri, Jun 12, 2020, 01:33 Geoffrey Cleaves ***@***.***> wrote:
Hi, I'm getting the same error and the link you reference is not
available. Any other tips you can offer? I'm actually using Docker and it
looks like ahem.js reads environment variables, is that right. Will using
env variables solve the problem? I'd rather use a json file anyway so
please let us know the correct way to configure. Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65WUQUUPBOC5AUGBQGTRWFLTLANCNFSM4KLYKHRA>
.
|
I've got the Docker container working using environment variables. But I get the JSON error when not using variables. Does ahem.js read properties.json from somewhere? Where would I need to put the file? To answer your question, the (test) token is: Cheers! |
You can put the properties in a file called
.env
In the root of the project.
If documentation still refers tk properties.json i eill fix that.
…On Fri, Jun 12, 2020, 01:57 Geoffrey Cleaves ***@***.***> wrote:
I've got the Docker container working using environment variables. But I
get the JSON error when not using variables. Does ahem.js read
properties.json from somewhere? Where would I need to put the file?
To answer your question, the (test) token is: ui6 380 yTqC1w . It works
fine as an env variable, so I don't think that's the problem. I think my
problem is that my properties.json is not being found.
Cheers!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65SH32HZ7JXPVVJTXBDRWFOORANCNFSM4KLYKHRA>
.
|
I'll try documenting my step-by-step later so you can see what I might of done wrong. I did have an .env file but maybe in the wrong place. |
https://github.com/o4oren/Ad-Hoc-Email-Server/blob/master/README.md
I se it is documented correctly.
Look here.
…On Fri, Jun 12, 2020, 09:34 Geoffrey Cleaves ***@***.***> wrote:
I'll try documenting my step-by-step later so you can see what I might of
done wrong. I did have an .env file but maybe in the wrong place.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65QVDBUABRS3R46FN4TRWHEAZANCNFSM4KLYKHRA>
.
|
I see the error of my ways, thanks. |
Read the documentation.
I assume you didn't configure the token secret right.
…On Wed, Jul 22, 2020, 03:09 NomadSU ***@***.***> wrote:
I have the same problem if installing without docker.
I have used this software before
I Installed this using docker
Now I have another problem
Editing package.json gives no results
I cannot add domains
After editing package.json, it looks like it was not edited
http://airon116.biz:3000/api/properties
By clicking on this link, you can see that the properties.json is in its
original state
This is not true, I edited the file
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFTF65QT6GIQKYI6EYS2ZMTR4YU3ZANCNFSM4KLYKHRA>
.
|
Hey I'm getting this error, what should I do? I am a python programmer who does basic things, so if I have no idea what I'm taking about please don't instantly start throwing code at me :) |
Hi
I followed this article and followed step by step process but still getting this error in the end
node version v11.5.0
npm version 6.7.0
The text was updated successfully, but these errors were encountered: