Setting up with the Symfony Local Web Server

... 85 % free space and 95 % free inodes ...

It only runs as root.
As a regular user, it creates the log files inside $HOME/.symfony/log, but it cannot start the server ...

Hey Facundo,

Were you able to got it working? Probably "chown" the log file to the current user will solve the problem with permissions. I installed symfony CLI w/o sudo and it works for me. If you still have any problems with it - please, share some output so we see more context.

Cheers!

Actually, the log directory and files are created with my user.
Here is the sequence of what I do, and the result:

$ symfony server:start -d

[WARNING] run "symfony server:ca:install" first if you want to run the web server with TLS support, or use "--no-tls"
to avoid this warning
Impossible to go to the background
Continue in foreground
WARNING Web Server log file cannot be tailed: unable to watch log file: no space left on device
no space left on device

Inside my $HOME/.symfony/log:

$ ls -l

total 8
drwxr-xr-x 2 facundo facundo 4096 Sep 23 10:14 355fcc099c030d9fdf46ccacf80a13a5c57d076e
-rw-r--r-- 1 facundo facundo 441 Sep 23 10:14 355fcc099c030d9fdf46ccacf80a13a5c57d076e.log

ls -l 355fcc099c030d9fdf46ccacf80a13a5c57d076e/

-rw-r--r-- 1 facundo facundo 0 Sep 23 10:14 53fb8ec204547646acb3461995e4da5a54cc7575.log

As you can see, all files and directories are created with my running user.
I even tried changing permissions to 777, but with the same result.

- freespace on disk is about 85%
- free inodes is about 95 %
- symfony cli installed with my running user
- before yesterday's update it was all runing ok
- running as root seems to work ok
- o.s. is Debian 10.5
- php version is 7.3.19
- symfony cli version is (2020-09-22T10:45:38+0000 - stable)

Is there any other test / info that might help ?

Thanks.

Hey Facundo ariel P.!

Yea, this looks super weird - definitely like a bug. And one key thing you said is that it worked *before* the update (so, I'm guessing it worked when you had 4.18.4 of the symfony binary and now 4.19.0 is broken). I'd open an issue with this info here - https://github.com/symfony/cli

Unfortunately, the symfony binary is a small piece of not-open source code... so even I can't dive into it and debug what's going on.

Cheers!

I've try it in a brand new installed system and it works.
I think it might be something with my installation. The rare thing is I think I did not change anything in the middle.
I'll keep trying to solve it.
Thanks.

Let us know if you keep getting problems

Hey Ricardo,

Are you talking about Symfony console, i.e. bin/console? If so - you're on the wrong way, you need to use Symfony CLI client that we use in this course. It's a standalone application that you need to download from https://symfony.com/download - find a way to do this for your OS, and then follow hints from the installer. When you install it and move to the "/usr/local/bin/" - you can run the server with "symfony serve" command. And "symfony server:ca:install" command will be available as well for you.

P.S. So the "bin/console" Symfony Console component and the new Symfony CLI client are different things :)

Cheers!

Hey Victor,

Had the Symfony CLI installed, ran self-update, all good, ran the symfony serve command and got that error. Couldn't figure out what was going on so I downloaded again the Symfony Cli and this time it worked. Don't know why it didn't work the first time but well, at least it's working now.

Thanks for the help.

Cheers

Hey Ricardo manuel de faria silva gonçalves!

Hmm, super weird! Good though to just reinstall from scratch - it indeed could have been some legitimate issue with the library :).

Cheers!

Hey there,

That's a good question. Usually we upgrade our tutorials so they can work with newer PHP versions but that's not always possible, and this is one of those cases, that's why we advertise this tutorial is compatible only with PHP 7. What you can do is to also install PHP 7 in your local machine. If you're using Docker, that's a trivial task to do :)

Cheers!

Hey Team P.!

Do you mean just "make sure it's enabled?" or for actual breakpoint debugging? If it's about the first question, the Symfony binary is pretty smart about finding various PHP binaries on your system (check symfony local:php:list) and you can choose between which version to use with a .php-version file.

If you're talking about breakpoint debugging, there shouldn't be any special setup - but check this out for details - https://github.com/symfony/cli/issues/50 - and let me know if it helps.

Cheers!

Hey Facundo ariel P.

WARNING Web Server log file cannot be tailed: unable to watch log file: no space left on device
no space left on device "

That warning makes me think that you ran out of disk space in your computer? Can you double-check that please

And, about the other message Impossible to go to the background Continue in foreground I got it too some times and I fix it by restarting the web server

Cheers!

Hey Michael de`Oz

What server name are you speaking about? Is it about host name option? you can find some information here https://symfony.com/doc/cur...
or it's something else?

Cheers!

Hey Jean M.!

I just saw your question over on the other chapter and replied :). https://symfonycasts.com/sc...

Cheers!

Hey ojtouch

Yes, I think you have to install that library in order to generate a "valid" certificate for your localhost

Cheers!

Hey Dung L.

I believe Symfony local web-server uses the php.ini file from your CLI installation. Just locate that file and tweak it so we can be sure :)
Also, I recommend you to read this documentation in case you want to change PHP config only to a specific project https://symfony.com/doc/cur...

Cheers!

MolloKhan thank you! that is it! made the change in php.ini - it works, as well thanks for the bonus url above, it will come handy as I dive deeper into fun Symfony! :)

Hey Moh H. ,

What's the deal? I only see "Hhhm" in your comment :)

Cheers!

Hey Cavisv,

Well, first of all, you can try to load the page without SSL, i.e. use HTTP instead HTTPS for the protocol. Does the http://localhost:8000 works for you?

In this course we suggest to use "symfony serve" command instead of the old "bin/console server:run" one. Do you use "symfony serve"? What version of "symfony" CLI do you have? You can check with "symfony -v". Probably updating to the latest version may fix the problem. Also, could you try the same https://localhost:8000 URL in Google Chrome instead of Firefox? Does it work there?

Cheers!

After doing a Symfony update it works!
Only there remains an error SEC_ERROR_UNKNOWN_ISSUER
But I can click through that.
Thanks

Hey Cavisv,

Great, glad it helps! Unfortunately, I don't use Windows, can't help more with this error. If you still have this issue - feel free to report it to Symfony, I think they can help with it.

Cheers!

Thanks for the quick reply!

Yes, I was already using http, that works fine.

I use "symfony serve"

symfony -v gives "Symfony CLI version v4.5.2 (c) 2017-2019 Symfony SAS"

I already tried Chrome, that gives ERR_SSL_PROTOCOL_ERROR

Hey Skylar

Yes, you totally can. Just run bin/console server:start 0.0.0.0:80

Cheers!

Thank you for the reply. But I wanted to user Symfony Serve to get https. AFAIK, the console server only does http.

Hey Scottie,

Yes, Symfony server via bin/console supports only HTTP, you need to use "symfony serve" for HTTPS support. And you can specify a port explicitly like:
$ symfony serve --port=80

You can try it, but probably you would need to run this command with sudo to grant access for this, though it depends on your OS.

P.S. to know more about any command - run the command with --help at the end, like:
$ symfony serve --help

What about the IP - not sure if it's possible, at least I don't see it in the help output.

Cheers!

Thank you for your, Victor. I was hoping for a secret command line argument like sudo /home/sgutman/.symfony/bin/symfony serve --port=80 --host:0.0.0.0. Unforturnately, that did not work. Maybe in the future. Again, thanks.

Hey msthzn

That's a problem between your DB version and the DB charset. You have 2 options

1) Update to MySQL 5.6 or higher

2) Set the field's length to 181 (or is it 191? I don't remember, but you can play with that number)

Cheers!

Never-mind. I needed to download and install the "read the instructions in full" command...

Hey Steve,

Haha, glad you found the solution ;)

Cheers!

Yo Dan_M!

Hmm... interesting! Well, let's do some digging :). Ultimately, your Webpack Encore assets are just normal, boring, physical files inside your public/ directory after they're built - so nothing "weird" should be happening. I'd try this:

1) Restart the new symfony server and browser to your app
2) View source (or inspect element), copy one of the paths to your assets - css or JS - and surf to it - so it'll be something like https://localhost/build/app.css. Do you see the contents or some error?

The first difference that comes to mind with the two setups is that the symfony server gives you https, instead of http. I can't think why that would effect things - but it possibly may. Also, do you see any errors in your browser's console?

Cheers!

Hey Ryan,

My template has:

        {% block stylesheets %}
            <link rel="stylesheet" href="{{ asset('build/app.css') }}" />
        {% endblock %}

When I view source, I see`
<link rel="stylesheet" href="/build/app.73e7f49c.css" />`

When I click on the link, the stylesheet is downloaded as an attachment, and I see the following in my console:

Resource interpreted as Stylesheet but transferred with MIME type application/x-css: "https://localhost:8000/build/app.73e7f49c.css".```


I don't get it!

Dan

Hey Dan,

Hm, what browser do you use? Could you try in a different browser? Or in incognito mode for example? And what HTML doctype do you have in your base layout, is it:

<!doctype html>
<html>...</html>

Try to explicitly specify type of the loaded file as:

<link rel="stylesheet" type="text/css" href="{{ asset('build/app.css') }}">

Does it help?

Cheers!

Victor,

The doctype is just as you showed. I added the explicit type definition, and that did not change anything.

I use Chrome normally, but I tested in Edge and got the same result.

When I run encore dev-server, the stylesheet link resolves as:

<link rel="stylesheet" type="text/css" href="http://localhost:8080/build/app.css" />```


The stylesheet loads and everything works perfectly. 

When I run `encore production`, the stylesheet link resolves as: 

<link rel="stylesheet" type="text/css" href="/build/app.73e7f49c.css" />`

and the stylesheet won't load and throws the warning I showed earlier.

To leave no stone unturned, I changed my template so it would render as`
href="localhost:8080/build...`
but that did not make a difference.

I hope you can see a problem that I can't. Thanks!

Hey Dan_M !

Awesome digging :). I think this is a problem with the new Symfony server -that's my instinct. There are a few reasons. When you use Encore in the "normal" mode (not dev-server), it writes physically files. So... if there is any issue downloading then, that's really the fault of your "web server". I further think this because you said that bin/console server:run does serve them correctly - the problem is only with the symfony serve command. When you use the dev-server command in Encore, your files are served by a totally separate Node server - so it does make sense that they would work in that context, but not in the normal "build" context.

Let's experiment: try running the server like this:

symfony serve --no-tls

That will start the web server simply in http instead of https. I don't have any specific reason why I think that might make a difference - but let's try it. Beyond that, I think we should explore having you open an issue about this. Oh, one other thing to try is simply creating a public/build/foo.css file manually and putting some CSS in it. If you manually add a link tag in your template to this, does it download? Or do you get the same error.

Cheers!

Hey weaverryan

I tried symfony server --no-tls and got the same result. I also tried to call the compiled css file directly as <link rel="stylesheet" type="text/css" href="/build/app.css" /> with the same result. Then I replaced app.css with a very simple css file, just in case. Again, same result.

This perplexing!